No, unfortunately not. I tested many of the nearest and most obvious objects, but they all came up clean (and injected a test loop just to verify that it would indeed identify one, which it did.) By accident I noticed a 1 year old note from the original developers about a memory leak fix for a far-distant class and that turned out to be it.
Jim Eshelman www.nepm.net Network Monitoring with a Difference ----- Original Message ----- From: "Andy Lester" <[EMAIL PROTECTED]> To: "James Eshelman" <[EMAIL PROTECTED]> Cc: <[email protected]> Sent: 03/31/2006 9:46 PM Subject: Re: [Boston.pm] Finding cause of a memory leak in a module? On Mar 14, 2006, at 2:56 PM, James Eshelman wrote: > Looks like just what I need -- thanks Andy. Did it find a problem? -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
