I don't think you're experiencing a leak per se.

On my iBook starting 100 threads without loading any additional Perl modules apart from "use threads" costs more than 31 Mbyte of memory. You might want to check this for yourself with my Benchmark::Thread::Size module like this:

$ perl -MBenchmark::Thread::Size=refonly # (ref) + 0 1728 1 2101 2 2398 5 3288 10 4780 20 7753 50 16685 100 31572
Your sample code seems to want to start 1000 threads. Be prepared to have at least 315 Mbyte of memory available for that. Unfortunately, in my experience, any serious program very quickly takes at least 1 Mbyte per thread. So you better have a lot of RAM available if you want to start 1000 threads that way.

You might also be interested in an article that I wrote about this earlier.

Liz


In reply to Re: A Memory Leak in Perl iThreads? by liz
in thread A Memory Leak in Perl iThreads? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.