Measure memory usage in Visual Studio (C#, Visual Basic, C++, F#)
Applies to: Visual Studio Visual Studio for Mac
This article applies to Visual Studio 2017. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here
Find memory leaks and inefficient memory while you're debugging with the debugger-integrated Memory Usage diagnostic tool. The Memory Usage tool lets you take one or more snapshots of the managed and native memory heap to help understand the memory usage impact of object types. You can also analyze memory usage without a debugger attached or by targeting a running app. For more information, see Run profiling tools with or without the debugger. For information on choosing the best memory analysis tool for your needs, see Choose a memory analysis tool.
Although you can collect memory snapshots at any time in the Memory Usage tool, you can use the Visual Studio debugger to control how your application executes while investigating performance issues. Setting breakpoints, stepping, Break All, and other debugger actions can help you focus your performance investigations on the code paths that are most relevant. Performing those actions while your app is running can eliminate the noise from the code that doesn't interest you and can significantly reduce the amount of time it takes you to diagnose an issue.
The debugger-integrated Diagnostics Tools are supported for .NET development in Visual Studio, including ASP.NET, ASP.NET Core, native/C++ development, and mixed mode (.NET and native) apps. Windows 8 and later is required to run profiling tools with the debugger (Diagnostic Tools window).
In this tutorial, you will:
- Take snapshots of memory
- Analyze memory usage data
If Memory Usage does not give you the data that you need, other profiling tools in the Performance Profiler provide different kinds of information that might be helpful to you. In many cases, the performance bottleneck of your application may be caused by something other than your memory, such as CPU, rendering UI, or network request time.
Custom Allocator Support The native memory profiler works by collecting allocation ETW event data emitted during run time. Allocators in the CRT and Windows SDK have been annotated at the source level so that their allocation data can be captured. If you are writing your own allocators, then any functions that return a pointer to newly allocated heap memory can be decorated with __declspec(allocator), as seen in this example for myMalloc:
__declspec(allocator) void* myMalloc(size_t size)
Collect memory usage data
Open the project you want to debug in Visual Studio and set a breakpoint in your app at the point where you want to begin examining memory usage.
If you have an area where you suspect a memory issue, set the first breakpoint before the memory issue occurs.
Because it can be challenging to capture the memory profile of an operation that interests you when your app frequently allocates and de-allocates memory, set breakpoints at the start and end of the operation (or step through the operation) to find the exact point that memory changed.
Set a second breakpoint at the end of the function or region of code that you want to analyze (or after a suspected memory issue occurs).
The Diagnostic Tools window appears automatically unless you have turned it off. To bring up the window again, click Debug > Windows > Show Diagnostic Tools.
Choose Memory Usage with the Select Tools setting on the toolbar.
Click Debug / Start Debugging (or Start on the toolbar, or F5).
When the app finishes loading, the Summary view of the Diagnostics Tools appears.
To take a snapshot at the start of your debugging session, choose Take snapshot on the Memory Usage summary toolbar. (It may help to set a breakpoint here as well.)
To create a baseline for memory comparisons, consider taking a snapshot at the start of your debugging session.
Run the scenario that will cause your first breakpoint to be hit.
While the debugger is paused at the first breakpoint, choose Take snapshot on the Memory Usage summary toolbar.
Press F5 to run the app to your second breakpoint.
Now, take another snapshot.
At this point, you can begin to analyze the data.
Analyze memory usage data
The rows of Memory Usage summary table lists the snapshots that you have taken during the debugging session and provides links to more detailed views.
The name of the columns depend on the debugging mode you choose in the project properties: .NET, native, or mixed (both .NET and native).
The Objects (Diff) and Allocations (Diff) columns display the number of objects in .NET and native memory when the snapshot was taken.
The Heap Size (Diff) column displays the number of bytes in the .NET and native heaps
When you have taken multiple snapshots, the cells of the summary table include the change in the value between the row snapshot and the previous snapshot.
To analyze memory usage, click one of the links that opens up a detailed report of memory usage:
- To view details of the difference between the current snapshot and the previous snapshot, choose the change link to the left of the arrow (). A red arrow indicates an increase in memory usage, and a green arrow indicates a decrease.
To help identify memory issues more quickly, the diff reports are sorted by object types that increased the most in overall number (click the change link in Objects (Diff) column) or that increased the most in overall heap size (click the change link in Heap Size (Diff) column).
To view details of only the selected snapshot, click the non-change link.
The report appears in a separate window.
Managed types reports
Choose the current link of an Objects (Diff) or Allocations (Diff) cell in the Memory Usage summary table.
The top pane shows the count and size of the types in the snapshot, including the size of all objects that are referenced by the type (Inclusive Size).
The Paths to Root tree in the bottom pane displays the objects that reference the type selected in the upper pane. The .NET garbage collector cleans up the memory for an object only when the last type that references it has been released.
The Referenced Types tree displays the references that are held by the type selected in the upper pane.
To display the instances of a selected type in the upper pane, click on "View Instances" next to the object type.
The Instances view displays the instances of the selected object in the snapshot in the upper pane. The Paths to Root and Referenced Objects pane displays the objects that reference the selected instance and the types that the selected instance references. When the debugger is stopped at the point where the snapshot was taken, you can hover over the Value cell to display the values of the object in a tool tip.
Native type reports
Choose the current link of an Allocations (Diff) or Heap Size (Diff) cell in the Memory Usage summary table of the Diagnostic Tools window.
The Types View displays the number and size of the types in the snapshot.
Change (Diff) reports
Choose the change link in a cell of the summary table of the Memory Usage tab on the Diagnostic Tools window.
Choose a snapshot in the Compare To list of a managed or native report.
The change report adds columns (marked with (Diff)) to the base report that show the difference between the base snapshot value and the comparison snapshot. Here's how a Native Type View diff report might look:
Blogs and videos
In this tutorial, you've learned how to collect and analyze memory usage data. If you already completed the tour of the profiler, you may want to get a quick look at how to analyze CPU usage in your apps.