0

This old blog post describes how to diagnose memory issues using dump files. Unfortunately, the method described only works with Visual Studio Ultimate, which I don't have access to.

How could I extract similar information from a dump? Ideally, I'd like to know which objects are taking the most memory and where they are in the hierarchy of references. I don't really need to compare two dumps at this point.

I know how to use Diagnostic Tools window to get that information when debugging a live application, but I'm looking for a solution that works in a dump-only situation.

relatively_random
  • 4,505
  • 1
  • 26
  • 48
  • WinDBG can do it all, but you do have to learn some black magic: https://blogs.msdn.microsoft.com/paullou/2011/06/28/debugging-managed-code-memory-leak-with-memory-dump-using-windbg/ – jessehouwing Jan 18 '18 at 13:54
  • [use DebugDiag Analyzer](https://blogs.msdn.microsoft.com/benjaminperkins/2016/02/01/analyze-a-memory-dump-using-the-debug-diagnostic-tool/) and analyze the memory usage from the dumps – magicandre1981 Jan 18 '18 at 15:44
  • I would recommend to get normal paid memory profiler which appreciates your time and shows you what you want in two clicks. – Ed Pavlov Jan 22 '18 at 13:22

1 Answers1

1

If you don't want to use VS IDE, Windbg would be a better choice.

How do I use a dump file to diagnose a memory leak?

Of course, you could also think about using other tools, like PerfView or DebugDiag Analyzer:

Analyzing memory dump to find leak

Fletcher
  • 422
  • 1
  • 6
  • 21