in reply to MemLeak in Perl from C Calls
Hi Monks,
We are also facing the same problem.
The memory is growing like anything.
The only difference is, we are using call_pv() to invoke
the perl subroutine instead of perl_run().
We thought of posting the same question yesterday itself.
However, we couldn't.
When will the memory allocated by the perl be released,
during perl_destruct() or when the reference count to perl
variables (scalar/hash/list) becomes zero?.
Any suggestions or comments will be helpful.
Regards,
Poornachandran SM
Re: Re: MemLeak in Perl from C Calls
by tomw1975 (Sexton) on Jul 28, 2003 at 18:12 UTC
|
Was there any resolution to this? I have been having the exact same problem..... | [reply] [Watch: Dir/Any] |
|
Even after almost a decade, the problem exists as it was!
| [reply] [Watch: Dir/Any] |
|
Hi,
I'm facing the same problem...
It's ok since I can manage one call to perl_parse where memory leaks seems to be, with multiple call to perl_call_argv, but I'd like to have a clean memcheck output without using valgrind suppress option.
Still no answers (i.e. complete perl memory free on perl_destruct before program exit) ? (I'm on Perl 5.8.8)
Thanks...
| [reply] [Watch: Dir/Any] |
|