Re^3: sub DESTROY: Strange ordering of object destruction

in reply to Re^2: sub DESTROY: Strange ordering of object destruction
in thread sub DESTROY: Strange ordering of object destruction (SOLVED)

Maybe the object itself keeps itself alive? Maybe it has child objects that keep the parent alive too?

My guess is that your object SomeClass will never get released until global destruction.

My advice is to rip out code from SomeClass until it starts getting released at the appropriate time, and then slowly putting the code (and the SomeClass-internal calls to the code) back in until the leak reappears.

Comment on Re^3: sub DESTROY: Strange ordering of object destruction Download Code

Replies are listed 'Best First'.
Re^4: sub DESTROY: Strange ordering of object destruction by Anonymous Monk on Mar 03, 2011 at 12:07 UTC
Maybe the object itself keeps itself alive? Maybe it has child objects that keep the parent alive too? I find Data::Dump::Streamer can be really useful for finding out, I used it in HTML::TableExtract Memory Usage. Devel::Cycle might be quicker :)	[reply]

In Section Seekers of Perl Wisdom