ANTS Memory Profiler 10.2 introduced a beta support for analyzing process memory dumps.

Getting started

Creating a memory dump

You can create a memory dump by opening a Task Manager, then right-clicking your .NET application on the Details page and clicking Create dump file:

The memory dump will be created in a user temporary directory (e.g. %TEMP%\ConsoleApp10.DMP).

Depending on the environment, different ways to create a memory dump may be available (e.g. on Azure).

Loading a memory dump

To get started, click Open memory dump button on the main screen:

You can choose any .dmp file containing a memory dump of a managed .NET application.

Analyzing memory dump data

After a memory dump is loaded, you can analyze it the same way you would analyze profiling data from a regular profiling session.

For more information, see:

• The timeline
• The summary page
  • The Assemblies loaded in the CLR pop-up
• The class list
• The instance categorizer
• The instance list
• The instance retention graph
• Object filters
  • Working with basic filters
  • Suggestions for using filters
  • Filtering by object type
  • Filtering by reference
• Opening classes in Visual Studio

Current limitations

As reading memory dumps is still under development, some data may be incomplete.

• Memory dumps of 64-bit applications can only be opened when running AMP in a 64-bit environment.
• Memory dumps of 32-bit applications can only be opened when running AMP in a 32-bit environment.
• Memory dumps of applications targeting .NET Framework 3.5 and older cannot be opened.
• When analyzing a memory dump, Instance retention graph can show limited data or errors.
• When analyzing a memory dump, tracking IDisposable objects is not yet possible.