-
There is a memory leak in my application. The memory consumption shoots up after a couple of days of running the application. I need to dump call stack information of each orphaned block address. How is it possible with WinDbg?
-
I tried referring to document created by my colleague, but I’m confused about how to specify the symbol path and stuff like that. It didn’t work out. Where can I get a step-by-step document.
There is a memory leak in my application. The memory consumption shoots up after
Share
You can use umdh.exe to capture and compare snapshots of the process before and after leak happens. This works best with Debug binaries – it will give you the callstacks of memory allocated between the 1st and the 2nd snapshot.
http://support.microsoft.com/kb/268343