Visual C++ provides built-in memory leak detection, but its capabilities are minimal at best. This memory leak detector was created as a free alternative to the built-in memory leak detector provided with Visual C++. Here are some of Visual Leak Detector's features, none of which exist in the built-in detector:
  • Provides a complete stack trace for each leaked block, including source file and line number information when available.
  • Detects most, if not all, types of in-process memory leaks including COM-based leaks, and pure Win32/Win64 heap-based leaks.
  • Selected modules (DLLs or even the main EXE) can be excluded from leak detection.
  • Provides complete data dumps (in hex and ASCII) of leaked blocks.
  • Customizable memory leak report: can be saved to a file or sent to the debugger and can include a variable level of detail.
Other after-market leak detectors for Visual C++ are already available. But most of the really popular ones, like Purify and BoundsChecker, are very expensive. A few free alternatives exist, but they're often too intrusive, restrictive, or unreliable. Visual Leak Detector is currently the only freely available memory leak detector for Visual C++ that provides all of the above professional-level features packaged neatly in an easy-to-use library.

Visual Leak Detector is licensed free of charge as a service to the Windows developer community. If you find it to be useful and would like to just say "Thanks!", or you think it stinks and would like to say "This thing sucks!", please feel free to write review for recent release. Or, if you'd prefer, you can contribute a small donation. Both are very appreciated.

Last edited Apr 4, 2011 at 7:54 PM by KindDragon, version 5


kasicass Oct 18, 2013 at 3:28 AM 
Excellent tool~ I like it :)

nbolton Jul 9, 2012 at 4:04 PM 
KindDragon, VLD is an excellent tool! I registered on CodePlex just to tell you that.

mainantagonist Jan 30, 2012 at 6:51 AM 
I found this tool to be very useful and easy to use. I think it's the number one free solution to the memory leaks problem in vs 2010. Thank you so much KindDragon.