Memory Chronicles: Manage, Trace and Fix Memory Leaks
summary
Shows how to reproduce production conditions, capture heap snapshots at cold start and after load, and compare them to spot objects that never GC; uses V8 Inspector / Chrome DevTools, highlights the distance column and naming functions for readable stacks. Explains core dumps and llnode but warns to match V8 versions, warns that server‑side rendering can start at 200–300 MB, and gives a concrete leak: leaving DB connections open causes steadily rising memory that only closing connections fixes.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:20a Node.js application before?
- 21:50Server Side Rendering (SSR)
- 24:01Monitoring tools
- 30:58Close your connections
- 31:24Look for agnostic serve pages solution
- 32:05Review you packages
- 32:59Keep naming you functions
- 33:37Check how reliable are your 3rd services
related talks
38mUnderstanding Memory Behavior on Nodejs
24mDemystifying Memory Leaks in JavaScript
31mMemory Leaks in JavaScript
46mTracking Down a Memory Leak
28mMemory Profiling for Mere Mortals
22mThe Hitchhiker's Guide to All Things Memory in JS
31mJavaScript memory management: Visual Guide
47mMemory Snapshots — not scary, actually useful