Check out this code. It looks like in a subroutine the clean up of lexical variables in a "if" statement is not done until after the sub exits: 
use strict;
package foo;
our $counter = 0;

sub new {
  my $class = shift;
  bless {id=>$counter++},$class;
}

sub DESTROY{
  my $self = shift;
  print "DESTROYING $self->{id}\n";
}

package main;

test();
print "Back in main\n";
sub test{
  print "Entering test\n";
  if (1) {
    my $foo = foo->new();
  }
  if (1) {
    my $foo = foo->new();
  }
  if (1) {
    my $foo = foo->new();
  }
  print "Leaving test\n";
}

__OUTPUT__
Entering test
Leaving test
DESTROYING 0
DESTROYING 1
DESTROYING 2
Back in Main

[download]
UPDATE The point of showing this code, is that maybe it is not a memory leak, but merely a delay in clean up

In reply to Re: Strange memory growth? by fletcher_the_dog
in thread Strange memory growth? by meetraz

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.