Memory Snapshots — not scary, actually useful
summary
Shows how to use real tools—Chrome DevTools, memlab, and Clinic.js—to profile Node/V8 memory, read and interpret heap snapshots, and find memory leaks. Explains practical workflows and techniques for taking and using snapshots to diagnose and fix memory problems.
AI-written summary · about
chapters (20)
- 0:00Welcome
- 1:10Introduction
- 2:14V8 memory leak hunting
- 3:37Memory monitoring in browser/Node.js
- 5:22Real-time GC tracing
- 6:26Object movement tracing
- 8:33Memory leak tools
- 11:25Rework setup and usage
- 14:58Node.js profiling with Clinic.js
- 16:29Tool recap
- 17:32What is a memory leak
- 18:15Chrome DevTools Memory tab
- 20:22Memory allocation by functions
- 22:05Snapshot data views
- 25:42Snapshot object categories
- 27:08Filtering and analyzing snapshots
- 28:33Snapshot comparison technique
- 31:46Reading memory snapshots
- 33:35Q&A
- 44:14Conclusion
related talks
35mMemory Chronicles: Manage, Trace and Fix Memory Leaks
31mMemory Leaks in JavaScript
45mHow to Track Memory in V8?
24mDemystifying Memory Leaks in JavaScript
26mThe Hitchhiker's Guide to All Things Memory in Javascript
39mWelcome to Mordor! Hunting Performance Issues in Node js
05mIn hope for better memory tools
38mUnderstanding Memory Behavior on Nodejs