Whitepaper on the Debug Diagnostic Tool v1.1

I have recently published a whitepaper on the Debug Diagnostic Tool v1.1 (Debugdiag) at the following location in the download center.

The whitepaper gives a detailed description of the tool. It explains the main components of the tool and their usage. It also provides Walkthroughs on how to configure the tool to get the right data and how to analyze it. Debug Diagnostic Tool v1.1 is currently available from this Microsoft web site.

Comments (3)

  1. I have put together a quick and dirty debug diag script for troubleshooting .net memory leaks. (attached

  2. michalka says:

    Hi Mouradl,

    First thank you for this informative paper 🙂

    We have a reproducible scenario where we run a specific component and we see that both virtual and private bytes are rising and not fully released. We want to use DebugDiag in order to trace the source of the leak and we have a few questions regarding how to use it.  

    You wrote:"DebugDiag has a memory leak monitoring feature designed to track memory allocations for a process. DebugDiag will inject a DLL into the specified process and monitor memory allocations over time. When it’s time to analyze a process for leaks, a dump is generated, and the dump is analyzed to determine which allocations are not being released and which are most likely causing memory leaks..."

    Does that mean that the information about the allocations is gathered from the injected dll? The memory dump is just for indicating when those allocations should have been released already?

    In that case, we can create a 'Memory and handle leak' rule for our process, run the scenario and take a memory dump when it ends, is that correct?

    Thank you,


Skip to main content