*Unless your code has passed a reference to the variables out of that scope and they have failed to let go of those references. That is, your code has done something that necessitates retention. There are a few special exceptions to do with optimisations for function lexicals also, but if they were the root of your problem, they would be known about by now.That's what I'm talking about. When varname goes out of scope, the name goes away and the refcount to the SV goes down by one. The problem I was refering to was obscure varnames/references that u don't know about holding the door open to the SV, thus preventing garbage collection. My second concern was when/where/how/if garbage collection takes place at all. It would be nice if there were a debugging feature where Perl would tell u when it gc'd something.
In reply to Re^8: Massive Perl Memory Leak
by wagnerc
in thread Massive Perl Memory Leak
by wagnerc
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |