in reply to Re^2: Serious memory leak when using LWP
in thread Serious memory leak when using LWP

If you notice that any package provides an explicit destructor method ... call it what you will ... USE it. "There must be a reason." If it doesn't, still explicitly set references to "undef" instead of just letting them go out of scope. Is this advice necessary? I don't know.
  • Comment on Re^3: Serious memory leak when using LWP

Replies are listed 'Best First'.
Re^4: Serious memory leak when using LWP
by Anonymous Monk on Mar 09, 2012 at 02:58 UTC

    delete() is not a destructor, the destructor never gets called because the reference count is not zero

[reply]

In Section Seekers of Perl Wisdom