First, I don't think you want to set up %tick_inf outside the foreach loop like that. If it's only used within the scope of a single pass through the loop, declare it inside the loop. And I think you want to clear the has by saying %tick_inf = () rather than undef'ing it, but I'm not certain about that.

Now, as for finding your leak, you have to do this the old-fashioned way: take stuff out until the problem goes away. Comment out a section of code, run the program, see if it still gets large or not. Keep doing that until you find the part that is making it grow. Then come back and get help fixing that specific piece.

In reply to Re: Leak Hunting by perrin
in thread Leak Hunting by the_slycer

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.