Tim Deschryver • 9/21/2020

Finding that C# memory leak

Read Original

The article details a developer's experience identifying and resolving a production memory leak in a C# .NET Core API. It covers the initial detection of abnormal memory growth, the use of .NET diagnostic tools (dotnet trace, counters, dump) to collect data, and the analysis of a memory dump file using dotMemory to pinpoint a file logger as the culprit consuming 3.5GB of memory.

0 comments
#debugging #memory leak #c
Finding that C# memory leak

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
The Beautiful Web
Jens Oliver Meiert • 2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane • 1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg • 1 votes
4
Wagon’s algorithm in Python
John D. Cook • 1 votes
5
An example conversation with Claude Code
Dumm Zeuch • 1 votes