in reply to Re^12: Consumes memory then crashs
in thread Consumes memory then crashs

This is your 500-do-nothing-useful-threads-as-fast-as-you-can-with-no-attempt-to-solve-either-the-OPs-problem-or-work-out-what-you-are-doing-wrong code.

Sorry, but I have neither time nor inclination to fence with someone who's purpose is anything but. to help.


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

Replies are listed 'Best First'.
Re^14: Consumes memory then crashs
by mbethke (Hermit) on Mar 26, 2012 at 21:05 UTC
    You missed the part where I provided a working implementation.
      I provided a working implementation

      To me, not to him.

      And an approach that relies on a 170+ module "framework" that requires a perl4-ish globals&call-backs style of programming that went out with the ark.

      And the OP has the choice of selecting your solution, or the mojo solution, or the threaded solution or the LWP::ParallelUA solution I also offered.

      If he elects to use the threaded solution, and encounters a problem with it and comes back, I'll help him solve it.