VC ++ in Visual Studio 2010: Release Builds Using the Debug Heap

I am comparing / optimizing a slow C ++ application, and taking some stacks, I found that the release build of my application uses a bunch of debugging, as some stack traces found indicate:

ntdll.dll!string "Enabling heap debug options\n"()  + 0x11056 bytes 

This is a 64-bit application running on Windows 7. I see two or three other complaints about this problem in the same environment on the Internet, but with no answers.

Does anyone know why Windows or Visual Studio will use a bunch of debugging for a C ++ build project?

+5
source share
1 answer

, ( ). , , .

+6

All Articles