~/talk

Deep .NET Debugging

Talkat NDC London 2017 · 2017-01-16..01-20· [dotnet]
slides:none on file

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

  1. 0:00Start
  2. 1:44User-mode dump Snapshot of a process and the memory it addresses
  3. 11:39GATHERING MEMORY DUMPS
  4. 14:20ANALYZING MEMORY DUMPS
  5. 24:13Check the event viewer Capture dump on crash Look at the faulting stack
  6. 36:32MEMORY LEAKS
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.