Hello,

I seem to be having an issue with CDB_File (0.96) I've reproduced this on OS-X 10.5.2, FreeBSD 7.1, and SuSe 10x, so I think it must be in the module and not system related. (Or, maybe, I'm using it wrong).

At any rate, here is some code:

use strict;

use CDB_File;


my $cdb_file = 'test.cdb';
my $cdb = CDB_File->new($cdb_file, "$cdb_file.tmp") or die "Unable to 
+create CDB file: $!";
while(1)
{
  $cdb->insert('leak', 1);
}

[download]

When this script runs the process's memory footprint grows larger and larger. I thought it might be related to re-inserting the same key over-and-over, so I changed it to something like 'leak'.$i and observed the same behavior.

I reported this as a bug at rt.cpan.org, but thought maybe I'd post it here in case other's had (or have, or will have) a similar issue and someone has a solution.

Thanks, as always!

- dEvNuL

In reply to CDB_File memory leak by devnul

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.