Two Minute Drill: UMDH.EXE

re: Two Minute Drill: UMDH.EXE

molotov — Tue, 08 Jul 2008 15:28:58 GMT

Good post about UMDH, Mike! Wonder if this may also lead into a discussion about DebugDiag and the Memory Pressure Analyzers? (Granted, we're awaiting the x64 version of DebugDiag, while apparently UMDH works with 64-bit processes...)

re: Two Minute Drill: UMDH.EXE

Syed Khairuddin — Wed, 09 Jul 2008 11:25:02 GMT

Its a great information Mike thanks for sharing it. It would be great if you can demonstrate and give the explaination about the memory leak using Performance Monitor.

Thanks

Syed

re: Two Minute Drill: UMDH.EXE

Syed Khairuddin — Wed, 09 Jul 2008 11:29:08 GMT

Hello Mike,

Its really a great piece of Information. It would be really great if you can give a screenshoted demonstration for Identifieng memory Leak's using

Performance monitor.

Thanks

Syed

re: Two Minute Drill: UMDH.EXE

Syed Khairuddin — Wed, 09 Jul 2008 11:29:24 GMT

Hello Mike,

Its really a great piece of Information. It would be really great if you can give a screenshoted demonstration for Identifieng memory Leak's using

Performance monitor.

Thanks

Syed

re: Two Minute Drill: UMDH.EXE

Lori — Tue, 12 Aug 2008 21:58:43 GMT

I get kern1l gflags: error: 5 when trying to set UST

re: Two Minute Drill: UMDH.EXE

lsalamon — Wed, 01 Oct 2008 16:39:17 GMT

What about "In a future post, we'll go over troubleshooting a memory leak using UMDH.EXE." ?

The future is now.

re: Two Minute Drill: UMDH.EXE

subu — Fri, 17 Oct 2008 08:57:47 GMT

Hi Mike,

I'm using umdh tool to find memory leaks.

when I take diff. of 2 log(dump) files, then in the diff. file, full path of the reference file is truncated. So getting exact location is difficult from it.

Is there any settings in umdh, where I can put maximum allowable path length?

Regards,

Subu

re: Two Minute Drill: UMDH.EXE

Lakshman Kumar — Thu, 11 Jun 2009 12:23:00 GMT

Is there any limitation in using the 64bit UMDH for monitoring mixed mode processes?

Even after enabling the stack trace, UMDH still reports following

Warning: (Restarted the process after enabling the trace)

Warning: UMDH didn't find any allocations that have stacks collected.

Warning: Use gflags to enable allocation stack collection.

Warning: Restart the application for the setting to be in effect.

Warning: A 64bit GFLAGS must be used. The command is:

Warning: gflags -i KTJOBO~1.EXE +ust

Warning: