in reply to Memory leak, and Devel::LeakTrace takes too long

Programs to track leaks often keep a database of every object allocated and deallocated, so for each object that gets created/deleted it has to update the database. The overhead can be considerable

Suggestion: Cut down the amount of the input data that you're feeding it, or cut it up into chunks if different classes of data get processed by different parts of the program. This may help to isolate the problem.

  • Comment on Re: Memory leak, and Devel::LeakTrace takes too long