The v2021.2 Releases for dotCover, dotMemory, dotTrace, and dotPeek Are Here!
Good news, everyone! We are happy to announce the release of the 2021.2 versions of dotCover, dotMemory, dotTrace, and dotPeek. Before diving into the feature set we’ve added in this release, there are a couple of important notes: Starting with the 2021.2 release of our .NET productivity tools, including dotCover, dotMemory, dotTrace, and dotPeek, we will require .NET Framewor
Improved Allocation Details and Powerful Type Filters in dotMemory 2021.2 EAP
With the release of dotMemory 2021.2 around the corner, we thought we'd give you, our loyal JetBrains customers, a sneak peek at some new and exciting features. These newest improvements will make you become a memory maestro in no time! We re-worked the allocation analysis views. Allocations grouped by methods and by call tree add more powerful filter options, and show top allocated types and b
Investigate memory issues with ease – Introducing real-time inspections in dotMemory Allocation Analysis
Memory issues can be challenging to diagnose, especially when we're under the stress of an extreme performance issue and unhappy users. Luckily, dotMemory 2021.1 users will appreciate the new and improved memory allocation analysis in our product's latest version. Using our new allocation analysis UI, we'll quickly locate those wasteful allocations bringing our application to a grinding halt. We'
dotTrace and dotMemory bring new home screen!
Longtime users of dotTrace and dotMemory may have noticed the brand new home screen that ships with version 2021.1. The change comes as part of our goal to make our products the best profiling tools on the market for all major desktop platforms (we're using Avalonia to make this cross-platform UI a reality). We redesigned the user interfaces to help developers jump right into a profiling session.
What Do These …<>+c… Classes Do in my Memory Snapshots?
There's nothing we love as much as user feedback. It is a priceless source of insights into how people use tools like dotMemory, what gets them excited – and what gets them confused. Over the last year we've received multiple questions from users seeing classes with ...+<>c... in their names. They said: "...in the object browser we have some instances of an object that ends with +<
How does my app allocate to LOH? Find out with dotMemory 2018.2!
If you're a long-term dotMemory user, you may have noticed the absence of big new features in dotMemory ever since we added support for memory dumps in 2017.2. Rest assured this is not because we've lost interest in memory profiling. The opposite is true: our team has been investing even more effort in this area, but most of the current changes are happening under the profiler's hood. One such