Re: Looking for Leaks

I must have missed something, MeowChow;

Are you looking for a way to monitor your system within the script to make sure it isn't gobbling up too much memory?

Or are you looking for a tool that will help you identify where the leak is occuring within the script?

Comment on Re: Looking for Leaks

Replies are listed 'Best First'.
(MeowChow) Re: Looking for Leaks by MeowChow (Vicar) on Aug 09, 2001 at 22:52 UTC
I'm looking for the latter. MeowChow s aamecha.s a..a\u$&owag.print	[reply]
Re: (MeowChow) Re: Looking for Leaks by dragonchild (Archbishop) on Aug 09, 2001 at 23:26 UTC
Well, isn't there a way/tool to, from the main section of the script, find out which memory locations aren't accessible? Everything should be accessible (except for closures) and all of that can be pointed out. You can then read through the output, mark off which you know to be closures, and then you have your answer... ------ /me wants to be the brightest bulb in the chandelier! Vote paco for President!	[reply]
Re: Re: (MeowChow) Re: Looking for Leaks by bikeNomad (Priest) on Aug 09, 2001 at 23:44 UTC
If things weren't accessible, how would you find them? At least in pure Perl, this would be impossible. You could iterate over all the symbol tables, following references to reachable objects, but this wouldn't find things that had leaked.	[reply]
Re: Re: Re: (MeowChow) Re: Looking for Leaks by dragonchild (Archbishop) on Aug 09, 2001 at 23:49 UTC


laziness, impatience, and hubris
	PerlMonks