Troubleshooting Node.js Applications Under the Hood
summary
Demonstrates practical debugging of Node.js native crashes and performance issues by creating a 1.3 GB core dump and analyzing it with llnode/LLDB or gdb plus V8 plugins to recover source, request and local variables and locate a missing rewards id. Shows heap scans and v8 find to trace forgotten timers that hold requests, and captures GC traces and event-loop samples to generate flame graphs that identify slow npm parsers; explains using GC/event-loop tracing and selective core-dump creation to avoid excessive dumps and long stop-the-world pauses, yielding large latency improvements (from 5× slowdown down to ~2× speedup).
AI-written summary · about
chapters (11)
- 0:00Node.js diagnostics
- 5:59Debugging in production
- 7:23Stack trace for errors
- 9:54Core dump tools
- 16:42Memory leaks via heap
- 21:19Detecting memory leaks
- 26:47On-demand core dump
- 32:23Performance profiling
- 40:50File system diagnostics
- 43:23Diagnostics fundamentals
- 46:55Q&A
related talks
25mNode js applications diagnostics under the hood
50mPost-Mortem Debugging in Node.js
28mPost mortem NodeJS debugging
50mDebugging Node.js in Production
28mSegmentation fault! Low-level debugging for JS developers
01h 04mNode.js performance analytics and best practices
38mWelcome to Mordor! Hunting Performance Issues in Node.js.
43mFinding memory leaks and CPU bottlenecks with Node.js debug tools