It is not easy at all to do what you're trying to accomplish, so you might be novice but not coward :D.
I wouldn't use Devel::Leak::Object at first because you have to provide it with a reference to an object, so you are making assumptions and it can take forever untill you hit the memory leak as spam assassin has thousands lines of code. Here is what I'd do
In reply to Re: How to detect and avoid memory leaks on Windows
by bluescreen
in thread How to detect and avoid memory leaks on Windows
by posti
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |