I ran into a memory leak in a system I'm working on

I see no leekage. Memory usage is more or less constant. 

#!/usr/bin/perl
use strict;
use warnings;

sub bar {
    if ( foo() ) {
        goto &bar;
    }
    return;
}

my $i;
sub foo {
    return $i++ < 500_000;
}

$i=0; bar(); print("Press Enter to continue"); <STDIN>;  # 32,824K
$i=0; bar(); print("Press Enter to continue"); <STDIN>;  # 32,872K
$i=0; bar(); print("Press Enter to continue"); <STDIN>;  # 32,860K
$i=0; bar(); print("Press Enter to continue"); <STDIN>;  # 32,856K

[download]

The stack and all lexical variables should be deallocated when goto is called, right?

Should? Dunno. Does? No. ( That's why the memory usage increases for each recursive call to bar. )

In reply to Re: memory leak when using tail recursion? by ikegami
in thread memory leak when using tail recursion? by juddhuck

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.