Using VLD2.5, and VS2015 on an empty project is showing 9 memory leaks.
I presume that this is a bug in VLD 2.5?
In VS2015 Enterprise, I've created an MFC Single Dialog app using the wizard.
Simply running the app, then closing the app reports leaks:
Visual Leak Detector detected 9 memory leaks (1656 bytes).
Largest number used: 13634 bytes.
Total allocations: 49384 bytes.
Visual Leak Detector is now exiting.
I've attached the complete output from VLD.
Comments: It's because vld unload order (linker unload vld before mfc). You can try workaround it by linking vld.lib directly to your project.
I presume that this is a bug in VLD 2.5?
In VS2015 Enterprise, I've created an MFC Single Dialog app using the wizard.
Simply running the app, then closing the app reports leaks:
Visual Leak Detector detected 9 memory leaks (1656 bytes).
Largest number used: 13634 bytes.
Total allocations: 49384 bytes.
Visual Leak Detector is now exiting.
I've attached the complete output from VLD.
Comments: It's because vld unload order (linker unload vld before mfc). You can try workaround it by linking vld.lib directly to your project.