I'm debugging a Winforms application for a memory leak. In the dump file provided by the customer there is a large discrepancy between the unknown memory usage and the .NET Heap size. (Approximately 1000mb vs 200mb). So what is in the unknown segment other than the VirtualAllocs done by the CLR?
!eeheap -gc output
!address -summary output
Memory that is reported as <unknown>
by WinDbg is memory that was allocated via VirtualAlloc()
. Some commonly known sources are:
VirtualAlloc()
calls in your codeHeapAlloc()
calls that are larger than some limit (512k if I recall correctly)If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With