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:

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

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.
Read more