CSI .NET – Debugging .NET Applications

on YouTube ↗01h 15m

" summary

Simulated leaks show 20,000 Product objects holding ~400 MB in char arrays; investigation uses dotnet-counters, dotnet-gcdump and dotnet-dump to create heap snapshots, then Visual Studio or WinDbg/SOS to follow root chains and thread stacks. Demonstrations expose LOH problems (objects > 85,000 bytes), finalizer-queue blocking, server mode with eight GC heaps, and a string-concatenation bug that continuously creates large objects causing repeated full GCs and high CPU.

AI-written summary · about

" chapters (9)

1. 0:00Introduction
2. 2:07Debugging high memory usage issues
3. 20:11Garbage collection: Roots
4. 25:37Garbage collection: Generations
5. 28:53Large Object Heap
6. 30:44Memory issues part 2
7. 39:55Debugging performance issues
8. 59:16Debugging crashes
9. 1:02:34Q&A

" related talks

• 53mDebugging .NET AppsTess Ferrandez-Norlander · NDC Oslo 2021
• 53mDeep .NET DebuggingTess Ferrandez-Norlander · NDC London 2017
• 50mDiagnostic techniques for .NET running on Linux and within containersMark Downie, Sam Spencer · Microsoft Build 2024
• 01h 05mLook Mommy, No GC!Dina Goldshtein · NDC London 2017
• 59mBuilding your own debugging toolbox with ClrMDChristophe Nasarre · DotNext 2018 Moscow
• 47mHow We Found a 2 GB/Day Leak in 5 Minutes – dotMemory Meets Akka.NETAaron Stannard · JetBrains .NET Days Online 2025
• 47mSolving .NET performance issuesAdam Sitnik · Update Conference Prague 2019
• 57mMake your custom .NET GC — "whys" and "hows"Konrad Kokosa · DotNext 2018 Moscow