What′s New in dotMemory
This page guides you through updates in recent dotMemory and dotMemory Unit releases. Highlights include a command-line profiling tool, support for .NET Core applications, and analyzing memory dumps.
.NET 5 support 2020.3
dotMemory now lets you profile .NET 5 applications on Windows, macOS, and Linux. Note that to profile applications on Linux and macOS, you should use dotMemory command-line profiler.
Timeline inspections 2020.3
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
Pinned object heap support 2020.3
.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.
Various timeline improvements 2020.3
- 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.
Support for ARM64 architecture 2020.2
The dotMemory command-line profiler for Linux (any distribution with GLIBC_2.23 or later) lets you profile applications on ARM64 systems.
View pinned objects 2020.2
You can now open pinned objects as a separate object set.
View unreachable objects 2020.2
You can now open objects that are not reachable from GC roots as a separate object set.
Various improvements 2020.1
In this release, we were focused on bugfixes and stability improvements.
Various improvements 2019.3
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.
Console profiler improvements 2019.2
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-activationargument 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.