debugdiag

Hello I have a leak in my WPF application and I'm trying to use the memory dump file to track down where the problem is. Using WinDbg and SOS I couldn't find anything suspicious. Then I tried DebugDiag and I got that Microsoft VC Runtime Heap (private) has 1,42 GBytes of commited memory. Do you know why does this happen? Heap 1 - 0x003b0000 Heap Name Microsoft VC Runtime Heap (private) Heap Description This is a private CRT heap used by mscoreei Reserved memory 1,43 GBytes Committed memory 1,42 GBytes(99,21% of reserved) Uncommitted memory 11,48 MBytes(0,79% of reserved) Number of heap

Feels like there's probably a simple answer to this, but I haven't been able to find it. The scenario in question is a C# .NET Console app. I commonly use DebugDiag 1.2 to examine .dmp files that come from hangs we experience - usually thread locking issues. They are created using DebugDiag's "Create Full Userdump" option. I recently began compiling the app targeting .NET 4 in preparation for starting to use some of .NET 4's features. However, I noticed that when analyzing these .dmp files with DebugDiag, all the .NET stack information is missing. If I change the CLR target back to .NET 3.5,

Visual Studio 2013 can show a column for inclusive size (which includes size of child objects) - http://blogs.msdn.com/b/visualstudioalm/archive/2013/10/16/net-memory-analysis-enhancements-in-visual-studio-2013.aspx DebugDiag's memory analysis reports currently only shows object size without including child objects. Is there a way to make DebugDiag include size of child objects in its report? What do you suggest is a good way to generate such a report for .NET 4.0 since Visual Studio only supports analyzing .NET 4.5 crash dumps DebugDiag DebugDiag 2 has totally been rewritten and is now a set

Over a year ago I already used WinDbg and DebugDiag to find a memory leak in a JNI native DLL that we use from within Java. Now I am searching for a thread handle leak. I created a memory dump using Process Explorer and tried to analyze it in DebugDiag, but all I get are script errors: I also tried WinDbg, but it is not able to attach to a process anymore. I always get the error message "dbghelp.dll has a version mismatch with the debugger": ("Unbekannter Fehler" means "Unknown error") I uninstalled DebugDiag and the Windows SDK, then downloaded the newest versions and installed Windows SDK 8

Recently I start facing issue on few servers where CPU start consuming more resources than usual trend. I am trying to find out the root cause for this and took the dump of w3wp process from Task Manager(right click on process and took the dump). Now the dmp file size is 14GB and I am trying to analyze it through WinDBG but the tool is not working and getting message: I also took few minidumps but some of them opening fine while few are not so it's not related to confusion between 32bit or 64bit.(The collected dump is 64bit). I am trying to know what causing this issue. Is it file size or I am