I noticed that the native C ++ application I'm working on has a fairly large amount of memory (20 MB) even before it goes into any of my codes.
(I mean the "private bytes" measure on Windows, which, as I understand it, is the most useful metric).
I set a breakpoint in the first line of the "main ()" function and, of course, at a distance of 20 MB when it reaches this.
The size of the EXE is only a couple of megabytes, so it does not take it into account.
I also intentionally deleted all the DLLs to prove that they were not the cause. As expected, it receives the message "Dll not found", but the trace remains 20 MB!
So, I thought that maybe these were the statically initialized objects that were the cause.
So, I added breakpoints for both "new" and "malloc". At the first hit on them (for the first static initializer), the memory is already 20 MB.
Does anyone have any ideas on how I can diagnose what is in this memory?
Since this seems like a memory outside of the usual new / malloc paradigm, I'm struggling to figure out how to debug.
Greetings
John
source
share