There is potentially a separate issue with apparent memory leaks in XML::DOM::Parser and those that may or may not have been fixed in XML::Parser. You may experience memory leaks in XML::DOM if you are creating many lexical DOM objects and just letting them go out of scope without caling the Dispose method on them before you do so, this is because there may be (intentional) circular references in the DOM object in memory. I have the same problem with XML::XSLT which uses XML::DOM under the covers and creates a number of DOM objects to hold intermediate results and parts of the template and so forth and it appears to leak like a sieve when processing a large number of documents with the same object.

/J\

In reply to Re: resolution of XML::DOM::Parser memory leak by gellyfish
in thread resolution of XML::DOM::Parser memory leak by wolis

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.