Finding that C# memory leak
Read OriginalThe 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.
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
No top articles yet