Hi to the hallowed!

I have had occasion to use Devel::LeakTrace::Fast in the head script of a suite and carped some interesting stats. Well, what to make of the stats is my current query.

Over 65,000 "leaks" are reported (the log is 5mb). Several thousand are from my own code, and there are some from installed modules also. A few questions to get me started occur straight away:

1. Are these "leaks" lost to the host system (reducing available memory until rebooted), or are they internal to perl in the sense they will be recovered by the host system when perl exits?

2. What significance should I otherwise attach to the stats. particularly the quantity involved.

3. Are the authors of leaky modules likely to be interested in hearing from me ..(over 5000 are recorded against Exporter.pm)..?

For some background, I am attempting to track down cumulative system degradation. KDE slows excruciatingly once the "free memory" reported by KSysGuard goes under 20mb, and I have noticed that then the "cache memory" and "buffer memory" reported has usually grown to a total over 300mb. This may not be anything to do with Perl, of course, but thought it a good place to start looking for eliminations!

I remain your wisdom sponge in these matters.

Pstack


In reply to memory sieve discovery by Pstack

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.