Author: If broken it is, fix it you should : ASP.NET | Posted on: 9/12/2008 6:21:05 AM | Views : 901

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,672 System.Drawing.Color 663bb5a0   16,530    1,454,640 System.Web.UI.WebControls...(read more) ...

Go to the complete details ...