As far as I can say, there is no memory leak in your program. It is just using a lot of memory if $i and $j become larger than simply 4 or 5 because is is recursing very deeply.

The quick way which might fix this program would be to replace:

use strict; print "what is the value of i:";
by:
use strict; use warnings; # it would have warned you about deep recursion use Memoize; memoize ('ackerman'); print "what is the value of i:";

BTW, your function is not the standard Ackermann function as I know it. Using a recursive form of the standard Ackermann function on values 3 and 5 (result = 253), the function is called 42438 times; with memoize, it is called only 636 times. With 3 and 6, the memoized vesion is called 1277 times, the non-memoized version 172233. But even with memoize, don't call it with large numbers.


In reply to Re: memory leak by Laurent_R
in thread memory leak by ch.sarath

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.