Skip to main content

Visual Studio 2022 - Check for memory leaks

When you see the memory usage increase in your applications, it can be a challenge to find the root cause. In that case capturing and analyzing memory dumps may be your last best option. In this post I'll show you how you can use Visual Studio to analyze your memory dumps.

Create a dump file

Before we can analyze a memory dump, we first need to create a dump file.

One way to do this is through the dotnet monitor command line tool or you can do it directly from the Task Manager by right-clicking on the desired process and choosing Create dump file:

Analyze the dump file in Visual Studio

Now that we have a dump file, we can open it in Visual Studio.

  • Open the dmp file in Visual Studio

  • Choose Debug Managed Memory from the list of actions. Visual Studio will try to load all the symbols and analyze all the memory information in the dump file. Be patient as this can take a while.

  • Once Visual Studio has done its work, you will see the Managed Memory viewer. This shows you all the object types found in memory, their number of occurrences, the size of these objects and their inclusive size.

That is already a good starting point to find out possible candidates that could cause a memory leak.

Compare 2 dump files

To help you in your investigation, it is also possible to compare 2 memory dumps and to see the differences. This is something I use a lot as it shows me exactly what is causing the increase in memory usage.

  • Click on the Compare with baseline dropdown and choose Browse…

  • This will open a file dialog where you can select another dump file. After selecting a second file click on Open to let Visual Studio load and process the file.
  • Once the processing has completed, the Managed Memory viewer shows some extra columns where you see the difference in number of occurences, size and inclusive size.

Happy debugging!

Remark: Also have a look at the following video:

Popular posts from this blog

XUnit - Assert.Collection

A colleague asked me to take a look at the following code inside a test project: My first guess would be that this code checks that the specified condition(the contains) is true for every element in the list.  This turns out not to be the case. The Assert.Collection expects a list of element inspectors, one for every item in the list. The first inspector is used to check the first item, the second inspector the second item and so on. The number of inspectors should match the number of elements in the list. An example: The behavior I expected could be achieved using the Assert.All method:

Angular --deploy-url and --base-href

As long you are running your Angular application at a root URL (e.g. www.myangularapp.com ) you don’t need to worry that much about either the ‘--deploy-url’ and ‘--base-href’ parameters. But once you want to serve your Angular application from a server sub folder(e.g. www.mywebsite.com/angularapp ) these parameters become important. --base-href If you deploy your Angular app to a subfolder, the ‘--base-href’ is important to generate the correct routes. This parameter will update the <base href> tag inside the index.html. For example, if the index.html is on the server at /angularapp/index.html , the base href should be set to <base href="/angularapp/"> . More information: https://angular.io/guide/deployment --deploy-url A second parameter that is important is ‘--deploy-url’. This parameter will update the generated url’s for our assets(scripts, css) inside the index.html. To make your assets available at /angularapp/, the deploy url should

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.