Author: Tess Ferrandez | Posted on: 10/9/2009 11:56:27 AM | Views : 1402

I got an email today on an issue that I think is pretty common when you try to memory leak analysis on a dump with debug diag.
They had set up a leak rule in debug diag to monitor for leaks and then ran the memory analysis on it to see what was leaking and the results looked something like this:
  Warning mscorwks.dll is responsible for 372.46 MBytes worth of outstanding allocations. The following are the top 2 memory consuming functions:
mscorwks!EEVirtualAlloc+119: 312.00 MBytes worth of outstanding allocations.
mscorwks!EEHeapAlloc+142: 60.46 MBytes worth of outstanding allocations. If this is unexpected, please contact the vendor of this module, M ...

Go to the complete details ...