In Release::Checklist, there's brief recommendation to use Test::LeakTrace as (re-phrasing) "help available to trace memory leaks to prevent crashes with out-of-memory after 4 days for long running process". OK.

use strict;
use warnings;
use Test::LeakTrace;
use Text::CSV_XS 'csv';

leaktrace {
    csv( in => \'1,2' );
};

[download]

This script produces a long list of 'leaks'. So what?

Then an example method_cache.pl, included with distribution, reports 'leaks' as well. I see nothing wrong with the code block. Shouldn't I use code like this?

The Test::LeakTrace is ++-ed and at stage 4 up river. Checking reverse dependencies, there's e.g. List::MoreUtils (up-river itself), but (maybe I'm wrong) dependency on Test::LeakTrace seems auto generated and not actually used.

In reply to How to use (interpret results from) Test::LeakTrace? by Anonymous Monk

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.