I like to try and do followups to my posts so that it serves as a solution database for others as much as possible. Often it takes some time though to find out what's going on before I post back a result.

After, dare I say, about 100+ hours of debugging on this problem my code was looking pretty clean (well clean enough). I then found out about Devel::Peek the other day (I love this module BTW) and went through most of the script checking the creation and destruction of my objects and variables all the way through, checking reference counts etc. All appeared good. Needless to say by now I was reaching the height of frustration.

It had occurred to me before that maybe what I was experiencing was a memory management issue with my OS(Win2000) so I re-image a PC at work with XP and ran my script on it across our Terabyte File Server. It ripped through the entire File Server in about 2 hours without breaking a sweat!!! Not a memory leak in sight.

So there you have it, my kung-fu was good, my OS was not! A lesson well learnt.


Dean
The Funkster of Mirth
Programming these days takes more than a lone avenger with a compiler. - sam
RFC1149: A Standard for the Transmission of IP Datagrams on Avian Carriers

In reply to Re: Memory Management and Array references by crabbdean
in thread Memory Management and Array references by crabbdean

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.