What′s New in dotMemory

In this release, we have continued to improve the way you analyze memory allocation. Two new tabs have been added to the Memory Allocation view:

• The Methods tab lets you analyze a plain list of methods that have allocated memory.
• The Call Tree tab lets you analyze the allocation call tree. Each node in the tree shows not only the called method but also the objects allocated by the call.

The search bar at the top of dotMemory views is now more flexible and easier to use:

• The filters have additional options for narrowing the search scope: #struct (search only in value types), #c (only in types), #m (only in methods), #ns (only in namespaces).
• You can get help for all filters possible in a given context.

It’s now possible to:

• Specify the traversal depth when exporting object data.
• Select one or more types and export their data to a single file.
• Export object data from the Instances, Outgoing References, and Unreachable Objects views.

We’ve completely reworked the dotMemory Home screen – it is much easier to configure and start new profiling sessions, work with snapshots, and perform other basic operations.

Now, you can analyze dumps of .NET Core applications collected on the Linux systems using gcore.

Now, dotMemory lets you analyze memory allocation on an arbitrary time interval. Just select the interval on the timeline and the Memory Allocation view will show you the objects allocated on this interval, as well as the stack trace that allocated them.

dotMemory uses the timeline data to provide automatic inspections right on the Timeline graph.

Currently, there are three inspections available:

• High Garbage Collection pressure
• Pinned objects in Gen0
• Fast Large Objects Heap growth rate

.NET 5 introduced a separate heap segment for storing pinned objects - objects that cannot be moved in a heap which leads to heap fragmentation. dotMemory shows the Pinned Object Heap in the Heap Fragmentation View. Also, now dotMemory shows memory allocated to the Pinned Object Heap in real-time during profiling.

• Garbage collections are shown on a separate graph below the main timeline.
• Now, you can select a particular time range on the timeline: The information about GC time and allocated memory will be shown for the selected time range.
• Performance improvements.

The dotMemory command-line profiler for Linux (any distribution with GLIBC_2.23 or later) lets you profile applications on ARM64 systems.

You can now open pinned objects as a separate object set.

You can now open objects that are not reachable from GC roots as a separate object set.

dotMemory 2019.3 gets a number of updates:

• The new self-profiling API (the API that lets applications initialize and start a profiling session by themselves) is much easier to use. The self-profiling API is distributed as a NuGet package.
• You can export details about a particular object instance to a file (.json, .bson, .txt, .hex).
• You can view a virtual memory address of an object instance.

dotMemory 2019.2 stops supporting remote profiling. To offer you an adequate replacement, we significantly improved the dotMemory console profiler:

• The console profiler gets commands to profile all types of applications including .NET Core applications, IIS Express-hosted applications, Windows services, and others.
• The --trigger-on-activation argument allows taking a memory snapshot right after this becomes possible. This feature can be helpful in case you want to take a baseline snapshot and use it for comparison.