Re^9: Memory leak questionby BrowserUk (Pope)
|on Oct 05, 2010 at 19:54 UTC||Need Help??|
Is there a good tool that I can use that will tell me every line number in the module where a variable was set to a new value and the old value was destroyed, but part of it hung around? Then, I could recursively destroy the old value before I created a new value (there's probably even a module to help me do this).
I'm the wrong person to ask. Most of the tools I've seen suggested for this--including Devel::LeakTrace & Devel::LeakTrace::Fast--don't run on my platform, so I've evolved other, source-code based, techniques.
I've seen many references to a *nix tool: valgrind, but I've no experience of it.
If you can send me a copy of your latest code, I could have a go using my limited techniques while you research the tools?
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.