How do you diagnose memory issues in .NET?

Question

Accepted Answer

**Memory diagnostics** — find leaks, high allocations, GC pressure. **dotnet-counters (live):** ```bash dotnet-counters monitor -p \ System.Runtime \ --counters gc-heap-size,gen-0-gc-count,gen-1-gc-count ``` **dotnet-dump (snapshot):** ```bash dotnet-dump collect -p dotnet-dump analyze > dumpheap -stat > gcroot

``` **Common issues:** - **Large object heap (LOH) fragmentation:** objects > 85KB. - **Event handler leaks:** subscribe without unsubscribe. - **Static references:** preventing GC collection. - **Caching without eviction:** growing memory. **Tips:** - Use WeakReference for optional caches. - Prefer ArrayPool for temporary buffers. - Enable Server GC for high-throughput apps.

C#: How do you diagnose memory issues in .NET?