WinDbg Address Summary

Question

Our wcf service hosted in IIS crashes (w3wp.exe ~ 1.6 GB) as the user load increases. We have got a dump through Debug Diag and ran this command in windbg. This is the outpu

Answer 1

About unclassified, a lot of posts on the Internet show that in late versions of WinDBG unclassified entries has just replaced the things that were mapped to different regions before. In previous versions of debugger you had these RegionUsageIsVAD, RegionUsageImage.

On my side, I also have a lot or unclassified entries in !address -summary output, but it doesn't prevent me from future debugging.

No, go back to your other results:

According to my experience with WinDBG, if eeheap shows ~300Mb of memory when MEM_COMMIT gives 1.3Gb, it could be a native memory leak.

See CodeProject on how you could catch it.

Note, that you possibly won't have stacks when running !heap -p -a, so you need to run your process with proper gflags before debug. You can read more about it

Then, you may possibly got another, simpler situation with repeated strings. I've run into such situation one time and described it.