Deep .NET Debugging
summary
Memory-dump debugging solves crashes, hangs, leaks and perf blips by showing the actual failing exception, roots and heap growth. Reproduced examples: an ArgumentOutOfRangeException crash exposed by loading SOS and using dumpheap -stat and gcroot; a low-CPU hang where eight threads sit in GetAllProducts discovered via Visual Studio/parallel stacks; a leak of 31,000 NewsController instances (~368 MB) traced to a cache callback. Tools and commands shown include ProcDump -ma, WinDbg/SOS, Visual Studio dumps, DebugDiag reports and automatable CLRMD scripts.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:44User-mode dump Snapshot of a process and the memory it addresses
- 11:39GATHERING MEMORY DUMPS
- 14:20ANALYZING MEMORY DUMPS
- 24:13Check the event viewer Capture dump on crash Look at the faulting stack
- 36:32MEMORY LEAKS
related talks
53mDebugging .NET Apps
01h 15mCSI .NET – Debugging .NET Applications
59mBuilding your own debugging toolbox with ClrMD
50mDiagnostic techniques for .NET running on Linux and within containers
57mExtend the new WinDbg to build your own dream debugging tool
53m.NET Debugging tricks you wish you knew
08h 53m.NET Days Online. Day 1
01h 00mC# Language Internals
