Debugging .NET Apps

on YouTube ↗53m

" summary

Demo-heavy troubleshooting that locates who holds memory and why it is not reclaimed, using concrete commands and artifacts: dotnet-counters to spot growing GC heap, dotnet-gcdump and dotnet-dump to list types (20,000 Product objects consuming ~402 MB) and run gcroot to find a static list root, Windbg/SOS and DebugDiag for finalizer-blocked cases (15,000 Link objects) and Visual Studio parallel-stacks for high-CPU/GC from large immutable string churn (>85,000 byte LOH).

AI-written summary · about

" chapters (4)

1. 0:00Start
2. 20:29DEMO GC MEMORY LAYOUT
3. 36:11BAD PERFORMANCE
4. 47:42CRASHES AND EXCEPTIONS

" related talks

• 01h 15mCSI .NET – Debugging .NET ApplicationsTess Ferrandez-Norlander · JetBrains .NET Days Online 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
• 59mBuilding your own debugging toolbox with ClrMDChristophe Nasarre · DotNext 2018 Moscow
• 01h 05mLook Mommy, No GC!Dina Goldshtein · NDC London 2017
• 01h 04mAdvanced .NET debugging techniques from real world investigationsKevin Gosse, Christophe Nasarre · NDC Oslo 2019
• 47mSolving .NET performance issuesAdam Sitnik · Update Conference Prague 2019
• 43mSelf-Aware Applications: Automatic Production MonitoringDina Goldshtein · Oredev 2017