http://qs1969.pair.com?node_id=75007


in reply to MemLeak in Perl from C Calls

Stefan, have you tried PL_perl_destruct_level = 1; before the loop? It's a global, documented in perlembed.

Replies are listed 'Best First'.
Re: Re: MemLeak in Perl from C Calls
by stefan k (Curate) on Apr 24, 2001 at 15:00 UTC
    Thanks for your guess, but it's still growing and growing in top :((

    I tried it at the beginning of main and right before the while-statement...

    Any other ideas?

    Regards Stefan K

[reply]
[d/l]
[select]

      No, as you say, you're using it pretty much as documented. Probably the best thing to do will be to keep the interpreter hanging around, and call perl_eval_ev() more than once - so in your loop, you get rid of the perl_construct/destruct, and put them outside the loop. That way, the memory you leak is constant, rather than proportional to the number of times you have looped. Not a fix, but a solution nonetheles...

[reply]
        Hi kal,
        first: thanks for your efforts!

        I tried this and the leak became invisible. But then I found that if you'd take away the sleep(1) it still grows.
        As a matter of fact: with the perl interpreter intitialising stuffed into main it grows only every 30 calls or something like that -> ?!?!

        Just to be sure I removed the call_perl()-statement from the loop and it didn't leak...

        Regards Stefan K

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom