Link Details

The CPAN is generally lacking when it comes to memory leak profiling. All the modules there are invasive, which means you have to guess where the leak is, and then see if you're right by adding some code to your application that will look for memory cycles within one data structure. This is inefficient, because Angerwhale is a big codebase, and I don't want to manually guess where the leaks are.