MemoScope.Net is an open-source, graphical tool designed to analyze .NET process memory dumps specifically to track down memory leaks and deadlocks. Built on top of Microsoft’s official ClrMD (Microsoft.Diagnostics.Runtime) library, it acts as a user-friendly, visual alternative to complex command-line debuggers like WinDbg. Key Features for Debugging Leaks
Visual Heap Analysis: Group and sort all instances in the managed heap by type, count, or total size to instantly identify memory-heavy objects.
GC Root Tracing: Trace any object back up its retention chain to discover exactly which long-lived object or static reference is preventing the Garbage Collector (GC) from reclaiming it.
Dump Comparison: Diff two separate memory dumps taken at different times to immediately see which objects are continuously growing in count and size.
Thread & Stack Inspection: View active application threads, their current call stacks, and the exact objects blocked on the stack. Step-by-Step Workflow to Fix a Memory Leak 1. Capture the Memory Dump
Before analyzing, you must take a snapshot of the application’s memory while it is experiencing high usage.
Windows Task Manager: Right-click your process under the Details tab and select Create dump file.
CLI Tools: Alternatively, capture a production-ready .dmp file using dotnet-dump via the command line: dotnet-dump collect –process-id Use code with caution. 2. Load the Dump in MemoScope Launch the MemoScope.Net.exe desktop UI. Go to File > Open Layout or open the .dmp file directly.
MemoScope will parse the dump using ClrMD and load the managed heap data. 3. Identify Bloated Objects (Type Stats) Finding MEMORY LEAKS in C# .NET Applications
Leave a Reply