Tom Perkins says:
I can't remember exactly what I searched for, but I was searching in Google for something like "C++ resource leak
detection" and I came across a link to your site. I am developing a little graphical shell for fun using other people's
code from CodeProject and some of this code hasn't been properly checked for memory / resource leaks. As the likes of
BoundsChecker, Rational PurifyPlus and CodeGlow are way too expensive for a little hobby project as well as not even
working in most cases (and too much overkill), Deleaker was the ideal choice.
Allan Kaminsky says:
Also, I should tell you that I originally used the trial version a few weeks ago. I liked its simplicity. I took some good code and purposely introduced a memory leak. I got immediate detection and useful information to easily pinpoint the faulty block.
I removed the trial and sampled some other packages. They were more complicated to use, more expensive, and (to my surprise) did not necessarily find the memory leak. When they did, they were difficult to use to locate the cause.
Brecht Moris says:
I was finishing a haptics project. It all worked out pretty fine, but I kept having problems with the memory usage.
I had some serious memory leaks, but I couldn't figure out where they where from.
I think it was the fourth application I tried but it was the definately my best choice.
It helped me fix my problem in no time. Most of the other applications that I tried before Deleaker took me some time to figure out.
I just like to keep it as simple and effective as possible. Deleaker offers both.