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.
dotMemory uses the timeline data to provide automatic inspections right on the Timeline graph.
Currently, there are three inspections available:
.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.
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.
In this release, we were focused on bugfixes and stability improvements.
dotMemory 2019.3 gets a number of updates:
dotMemory 2019.2 stops supporting remote profiling. To offer you an adequate replacement, we significantly improved the dotMemory console profiler:
--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.
Free trial for 5 days of actual use