Analyzing native memory allocation with dotTrace 2016.3

With C#, we live in a comfortable managed world where everything is controlled by CLR. But sometimes, whether we like it or not, we have to work with ‘unmanaged’ objects, for example when we want to use some third-party DLL, a COM component, or a resource required for interoperability with the operating system (like a bitmap).

dotTrace 2016.2 and earlier had no way of showing you how your application worked with unmanaged memory. Version 2016.3 introduced a new event type you can analyze – Native Memory Allocation. It can be very helpful with all kinds of issues related to native memory: potential memory leaks, issues with unmanaged components used by your managed code, and more.

The Native Memory Allocation filter simply shows all events where allocations to the native heap occur. Note that dotTrace currently shows you only allocations of native objects that were not de-allocated by the time you took the snapshot. Thus, unfortunately, at the current stage you cannot use this filter to analyze excessive native memory allocations (native memory traffic).

Native memory allocation point events

A couple of notes before we take a look at how it works:

  • You must have Windows Performance Toolkit installed on your machine.
  • dotTrace collects native allocation data only in the Timeline profiling mode.

How to use it

  1. First of all, when starting a profiling session, don’t forget to enable Collect native allocations in Advanced profiling options. (The option is disabled by default as it is a resource-consuming operation.)
    Advanced profiling options, Collect native allocations
  2. When you open a profiling snapshot in the viewer, select Native Memory Allocations in the Events list:
    Native memory allocation in Visual Studio
  3. Like nearly everything in dotTrace, Native Memory Allocation works as a filter. To identify calls that are responsible for native memory allocation, perform these two steps:
    1. Select the Native Memory Allocation event. Calls in the Methods window are now sorted by the size of native memory they allocate.
    2. Select a particular method and press Enter to navigate to its code.

Native allocations. Navigate to code

We hope you find this feature useful. To try it on your own, download ReSharper Ultimate 2016.3.

Comments below can no longer be edited.

3 Responses to Analyzing native memory allocation with dotTrace 2016.3

  1. Avatar

    Carsten Sponsel says:

    January 24, 2017

    I was very interested when i saw this new feature on twitter and immediately downloaded and installed the new version.
    Unfortunately collecting native allocation does not work, i get an internal ETW collector error:

    — Message #0

    ETW collector internal error


    Without native memory allocation the ETW collector (Timeline mode) seems to work.

    • Alexey Totin

      Alexey Totin says:

      January 24, 2017

      Hi Carsten!
      This looks like a bug. Could you please contact dotTrace support ( and send them logs from %localappdata%\Temp\JetLogs and %windir%\Temp\JetLogs folders?

  2. Avatar

    eugen_nw says:

    March 20, 2018

    It worked great for me, thanks very much for this handy functionality!

Discover more