I don't have a Solaris box at home so I can't test this, but I can give you a few tips though.

If Procfs is too blame, try creating a small test program that only calls psinfo, say a few thosuand times, and see if it grows out of proportion. If it does, you can pepper the Procfs.xs file(in the psinfo2hash function) with printf's. Make sure that all SV's stored in the hash have a reference count of 1. (Im a bit suspicious about the use of av_push in there. Anyone know if it increments the ref. count? ).

And of cource, take a look at the perlguts man page. The perlxs man page might be helpfull as well, if only to understand the "magic" statements in Procfs.xs

goldclaw

In reply to Re: Memory leaks by goldclaw
in thread Memory leaks by mikfire

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.