Sign in to follow this  
Samurai Jack

BoundChecker 7.2 Whoes

Recommended Posts

Greetings! I tried the Bound Checker 7.2 Memory Leak detection tool for Visual Studio yesterday, and I was very disappointed. An empty program a la "WINMAIN return 0;" produces from 128 bytes till 2K of memory leaks. How comes?! I am using Visual Studio .NET 2003. The same was under the intel compiler. In debug mode my EMPTY program leaks for 128 bytes and in Release additional 2048 bytes are leaking. The _CrtDumpMemoryLeaks() command shows nothing. If I allocate 4 kilos and leave them undestroyed, the statistics increase for additional 4 Kilos (128bytes + 4K) which should be OK, but why that 128 bytes and why that additional 2K in release?! Thank you in advance!

Share this post

Link to post
Share on other sites
What project did you exactly choose?
I just tested, created an empty win32 project and just added this:

#include <windows.h>


return 0;


Shows me no memory leaks at all.

Beware though: BoundsChecker likes to list static variables as leaks sometimes; and i have to agree with them: If BoundsChecker is not sure about the nature of a memory block being a leak or not, i'd rather have them listed.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this