We have purchased a single developer license for me to use here. Both my Boss and I were very pleased with Deleaker. It integrated well into visual studio, found all the issues we had with our code and was fast and, most importantly for us, was very light-weight in terms of effecting the product we are testing. It also gave stack traces that led me directly to the problems.
The plan is for me to run Deleaker once every few weeks or so, and fix all the issues it identifies.
I found Deleaker while searching for good Windows memory leak tools. Deleaker provided me with enough info to find and fix my leaks with minimal effort. I'm very glad I found Deleaker. The VS integration is great; it points me right to the offending allocations. Thanks for making a wonderful tool.
I found Deleaker when looking for a way to find memory leaks when using Visual Studio for C++ development. No other options were as effective and simple as Deleaker was. I was able to pinpoint the exact line where my problem was occurring and fix it quickly. Deleaker is an effective tool that I will now use with all my projects.
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.
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.