Leak detection used to be easier.

It's become complicated by the fact that OS's and programs will put off disposing of free'd blocks until "they feel like" it. Java is particularly troublesome about this. I've had to toss 100s of objects out of scope before I see their finalize methods finally start getting called.

You may want to try more interations. I've found that programs have to run awhile before their memory consumption levels off. There are artifacts in support libraries that keep their own private stashes of memory and don't start giving that up(if ever) until they've been used for a while.

I haven't used Purify for a while, are you certain that it managed to instrument the perl library as it was going along?

In reply to Re: Embedded Perl - Memory leak by ptkdb
in thread Embedded Perl - Memory leak by rajiyer

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.