in reply to eval + no warnings = no memory

Temporary "scratchpad" variables are not free()d until (roughly) the end of the statement. This statement never ends so each eval allocates a bit of temporary space and these never get free()d.

You can test this by making the loop only repeat a few hundred times and then put that in a bigger loop and see the memory grow initially but then level out as the hundreds of temporaries get free()d each time around the bigger loop.

But I haven't tested this theory, it just seems pretty danged likely. (:

        - tye (but my friends call me "Tye")
  • Comment on (tye)Re: eval + no warnings = no memory

Replies are listed 'Best First'.
Re: (tye)Re: eval + no warnings = no memory
by gryng (Hermit) on Jan 30, 2001 at 09:48 UTC
    I reduced the program to the smallest size, but I can assure you that the behavior happens even if the eval statement is within a loop, or even within a procedure called by a loop (as this was the original case).

    But it's a good guess though :)

    Ciao,
    Gryn

[reply]

      Ah, thanks for the info. From elsewhere in this thread, it sounds like the leak is in "stringy" eval for some versions of Perl on some platforms. I'm sure the porters would appreciate a bug report with the data collected so far. (:

              - tye (but my friends call me "Tye")
[reply]
        One of the benefits of perlmonks is that I can turn to you all for this sort of information: Where do you report bugs?

        Ciao,
        Gryn

[reply]

In Section Seekers of Perl Wisdom