Post-Mortem Debugging in Node.js
summary
Shows how to capture and analyze a Linux or macOS core dump to inspect live JS state, using llnode with lldb and V8 helpers to get JS stacks, object contents and surprising counts like 235000 visit objects that reveal leaks. Demonstrates generating dumps from a running PID, using node’s built‑in report (from Node.js 11.8) and writeHeapSnapshot to load snapshots into Chrome DevTools, and mentions an llnode JavaScript API that lets tooling read core files programmatically.
AI-written summary · about
chapters (10)
- 0:00Start
- 4:33Tools
- 7:54Core Dump Formats
- 8:22Generating a Core Dump
- 13:35Reproducibility
- 28:25Recap 1/2
- 29:02What are Memory Leaks in JS?
- 33:20Heap Dump Diffing
- 33:45Writing heap snapshots
- 40:58Working Areas
related talks
28mPost mortem NodeJS debugging
57mTroubleshooting Node.js Applications Under the Hood
25mNode js applications diagnostics under the hood
28mSegmentation fault! Low-level debugging for JS developers
50mDebugging Node.js in Production
43mFinding memory leaks and CPU bottlenecks with Node.js debug tools
23mBringing JavaScript Back to Life
14mExample Debugging Session using DTrace and MDB