Menu
Why I can not find "Debug Managed Memory" on Action menu as described at this MSDN article: Analyze .NET Framework memory issues?
My Visual Studio:
How it is supposed to look:
220
To debug kernel-mode dump files or use the SOS. dll debugging extension in Visual Studio, download the debugging tools for Windows in the Windows Driver Kit (WDK). Visual Studio can't debug dump files saved in the older, full user-mode dump format. A full user-mode dump is not the same as a dump with heap.
To open a dump file using Visual Studio: In Visual Studio, from the File menu, choose Open | Crash Dump . Navigate to the dump file you want to open. Select Open.
A dump file is a snapshot of an application at the point in time the dump is taken. It shows what was executing, what modules are loaded, and if saved with heap, contains a snapshot of what was in the application's memory at that point in time.
In one of the related articles, two requirements are mentioned (emphasis added):
Before I begin, there are a few things to note about the "Debug Managed Memory" feature discussed in this post:
- The option will only be available from the dump summary page in the Ultimate version of Visual Studio 2013. If you are using Premium or Professional you will not see the option.
- The process the dump file was collected against must have been running on .NET 4.5 or higher. If the dump was collected on 3.5 or previous the option will not appear, if it was collected on 4.0 it will fail to launch with an error message.
189
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
