Beyond step-by step debugging in Visual Studio
summary
Shows how to diagnose crashes, hangs, high CPU and leaks using real commands and examples: capture dumps with Task Manager, procdump or DebugDiag, inspect threads and managed stacks with WinDbg + SOS, list heaps and run !dumpheap / !gcroot to find 20,000 leaking controllers, and run DebugDiag rules to auto-report common patterns. Demonstrates Visual Studio opening a full dump, Visual Studio memory dump analysis and the profiler (instrumentation/sampling) to find waits and CPU hotspots; reproductions and working commands are shown.
AI-written summary · about
chapters (9)
- 0:00Introduction to dumps
- 2:11Windbg fundamentals
- 7:01Analyzing crash dumps
- 11:40Dotnet heap internals
- 17:35Collecting memory dumps
- 21:15Troubleshooting crashes
- 30:21Performance issues
- 40:47Profiling techniques
- 45:48Memory leak investigation
related talks
41mDebugging Tips and Tricks with Visual Studio
17mFast Focus: Visual Studio Debugging & Diagnostics: Tips & Tricks
01h 02mTime Travel Debugging
05mDebugging - A dive into Breakpoints
56mFuel Your Fixes: Visual Studio Debugging, Powered by Copilot
52mNew in Visual Studio: CMake Debugger, Better Diagnostics, and Video Games
01h 01mBack to Basics: Debugging in Cpp
35mBe Smug, Debug Why You Should Be a Delve Power User