Memory leak vanishes in the presence of VLD

Jun 22, 2012 at 9:30 AM
1) I get a memory leak - basic MFC wizard app 2) I install VLD 2.2.3 3) I change build settings so VLD include and lib/dll are picked up 4) I add #include <vld.h> to a key file 5) I build and run 6) my memory leak has gone away 7) I compare the output from MSVS with and without VLD - only diff is presence of dbghelp.dll and vld_x86.dll Any ideas as to how I should now proceed? TIA Neil
Jul 3, 2012 at 12:31 PM

Same over here. Suddenly my app has no leaks ... automagically patched by VLD 2.2.3? :)

Looks like a problem with buffering the output. I decided to check if 2.2.2 has the same problem, so I re-compiled the application. At the end of compilation, but before finishing, I got VLD output. And then report on successful build.


1>  Visual Leak Detector detected 85 memory leaks (17728 bytes).
1>  Largest number used: 108712 bytes.
1>  Total allocations: 153799 bytes.
1>  Visual Leak Detector is now exiting.
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

Build Summary
00:51.206 - Success - Debug Win32

Total build time: 00:51.287

========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========