Friday, 1 June 2012

How to gather dump with DebugDiag. Perfcounters.

As I often need to explain, how to create dumps, I'm going to create a small tutorial for each kind of them. Here we start.
If you experience kind of memory leak, when process is just eating memory without giving OOM or StackOverflow, it would be good to create a dump at the moment when used memory is already high, but not that high to induce an application shutdown or other unwanted consequences.

First of all, you need to download DebugDiag tool:

Then open DebugDiag 1.2 from your Start menu and here are your next steps:

If you experience an excessive memory usage:

If you have a process eating processor time:

Next steps after you choose needed performance counters and their thresholds:

After you start rule, run your faulting application for some time. When user dump is generated, DebugDiag will show "1" or "2" in its main dialog window, under UserDumps column. Then you may just open the folder  you set for dumps on the last step and get your nice .dmp file.


  1. Great - thank you for this. Have it occur constantly that CPU is maxed out and we can't dump the memory.

    1. Great if it helped. I love getting comments to these old posts :)