ANTS Memory Profiler 10

ANTS Memory Profiler 10.2 release notes

10.2.5 - January 15th, 2020


  • MP-2609: Profiling ASP.NET Core web applications hosted on IIS is now supported.

10.2.4 - November 28th, 2019


  • MP-2595: NullReferenceException should no longer occur when stopping the "Attach to .NET 4+ process" session. Attach to process sessions history is available again on the home screen.
  • PP-3778: Windows NT 10.0-based systems and their editions are now correctly recognized (Windows 10, Windows Server 2016, Windows Server 2019).
  • PP-3959: Profiling IIS applications is now supported on LTSC (LTSB) editions of Windows.

10.2.3 - October 1st, 2019


  • MP-2547, MP-2586: Memory dump analyzer no longer crashes when inspecting an instance of the class containing private fields with the same name as its base class.
  • MP-2574: After opening a memory dump, a New Profiling Session button will correctly display previous session settings instead of Unknown project type.
  • MP-2594: Memory dump analyzer will now show the appropriate message for memory dumps that are too large to open.

10.2.2 - August 1st, 2019


  • A missing dependency was added, whose absence prevented memory dump analyzer from working properly on machines without .NET Framework 4.7.0 or newer installed.

10.2.1 — July 10th, 2019


  • MP-2562: GC roots are now read by memory dump analyzer.


  • MP-2571, MP-2555: Fixed problems with accessing to instance categorizer for some types

10.2.0 — May 16th, 2019

With this release we have introduced support for analyzing process memory dumps. Whilst we have tried to ensure the best experience, this is considered a beta version and some features may not be fully implemented yet. Refer to the Known issues section for more information.

If you have any suggestions, don’t hesitate to use the feedback link inside the application. We’d love to hear your thoughts!


  • MP-1865: It's now possible to open and analyze memory dump files (*.dmp).

Known issues

  • 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.

Didn't find what you were looking for?