Reputation: 5166
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.
Upvotes: 0
Views: 2411
Reputation: 420
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
Upvotes: 1