What′s New in dotTrace

Navigation path in Call Tree 2017.2

When navigating a call tree, it's always been tough to understand how you ended up at a particular function. Not anymore with dotTrace 2017.2: the Call Tree view shows all your transitions in the left gutter.

Timeline profiling from the command line 2017.2

The command-line profiler finally supports the Timeline profiling type.

It's also worth noting that dotTrace command-line tools are now available as a NuGet package.

Profile child processes in unit tests 2017.2

You can now enable profiling of child processes in unit tests with a simple checkbox. Complex profiling configurations are no longer required!

Profiling in Visual Studio 2017 2017.1

dotTrace 2017.1, along with other products of the ReSharper Ultimate family, can now be installed into Visual Studio 2017.

Profile running apps with drag and drop 2017.1

You can now attach the profiler to running applications using drag and drop. Simply drop a special icon onto the application window that you want to profile.

Subsystems in Timeline Viewer 2016.3

In 2016.3, Timeline Viewer gets one of the greatest Performance Viewer's features: Subsystems.

The mechanics of Subsystems are quite simple: in most cases, each subsystem just groups calls made within a certain namespace or assembly. It is extremely useful when you need to quickly evaluate how time in a particular call subtree is distributed among various components: user and system code, WPF, LINQ, collections, strings, and more.

Subsystems are very flexible. If you use third-party frameworks in your solution, simply add the corresponding subsystems to dotTrace. Just a quick glance at the call's Subsystems will allow you to understand how much time this call spends in a particular framework.

Analyze native memory allocations 2016.3

dotTrace 2016.3 is able to collect data about memory allocations made to the native heap.

The Native Memory Allocation event filter allows you to see what methods are making the allocations and analyze all issues related to the native memory: potential memory leaks, issues with unmanaged components used by your managed code, and so on.

Analyze application's debug output 2016.3

dotTrace gets a new Debug Output filter which can be very helpful for advanced debugging. When selected, timeline will show you only events where your application writes to the debug output, e.g. with the Debug.Write system method.

Events window 2016.3

As the name suggests, the new Events tool window simply shows you event log — a list of events occurred in the profiled application: file operations, JIT, SQL queries, and more.

Use the window as you would use any other event log: to investigate complex cases and bugs when the data provided by other filters is not enough.

Profile .NET Core applications out of the box 2016.3

Now, if you have .NET Core tools installed on your computer, you can profile .NET Core applications without any additional actions.

The workflow is pretty straightforward. Simply select .NET Core Application on the Home page, specify the executable and click Run.

Improvements in Call Stack window 2016.3

The Call Stack window gets multiple improvements:

• We returned the Hide system functions option that was helpful in analyzing a method's own execution time.
• The methods list now shows total time in addition to every method's own time. Total time includes the execution time of the entire call subtree.
• You can now click on a method's own or total time in the methods list or call tree. This applies a filter by the corresponding method (if you clicked on the own time link) or by the method and its subtree (if you clicked on the total time link).
• The methods list can now follow your selection in Call Tree. When you select a particular method in Call Tree, the list of methods is rebuilt to only show child calls of the selected method.