We don't bite newbies here... much | |
PerlMonks |
Re: Profiling a large programby perrin (Chancellor) |
on Oct 27, 2006 at 19:36 UTC ( [id://581006]=note: print w/replies, xml ) | Need Help?? |
You can try PadWalker and Devel::Cycle for finding variables that are not getting freed. However, growth in memory doesn't always mean that you have memory leaks. It may just mean that you are loading something large into some of your variables at some point. The memory will stay allocated there one it has been used, even if the variable is garbage collected.
In Section
Seekers of Perl Wisdom
|
|