On Mar 14, 2006, at 2:35 PM, James Eshelman wrote: > I've got an O-O perl module that has recently developed a fairly > bad memory leak, presumably due to some new circular reference that > has been created and not cleaned up. Can anyone suggest any > methods or tools for narrowing a large initial list of potential > candidates down to the likely culprits? Anything faster than > trying to track down all the changes in cvs would be a gain.
Look at Devel::Cycle, and its testing wrapper Test::Memory::Cycle. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
