I was helping a colleague out with an OOM (OutOfMemory) situation he was dealing with.
Problem description:
Their applications memory usage would grow over time until they finally ended up with an out of memory exception.
First debug:
They had gotten a memory dump when memory usage was really high 1.4 GB using debug diag and I opened it up in windbg.exe, loaded up sos (.loadby sos mscorwks) and ran !dumpheap -stat to get the content of the GC heaps.
0:028> !dumpheap -stat
Statistics:
MT Count TotalSize Class Name
...
7ae77c54 59,028 1,416 ...
Go to the complete details ...