in reply to Threads: How to fix "Scalars leaked" Issue?

I believe the "leaked scalar" is the reference to %opts passed to the threads.

When I modified the code to pass the network, start, and stop parameters explicitly, instead of through the $args reference, the "leaked" message went away.

Replies are listed 'Best First'.
Re^2: Threads: How to fix "Scalars leaked" Issue?
by VinsWorldcom (Prior) on Nov 17, 2009 at 16:13 UTC

    ++ Votes for you! That fixed it for me too. I'm still curious as to why passing the hash and using the references gave issues?

    I was trying to make my life easier by passing a reference to a hash rather than each individual option.