Understand, find, prevent and fix memory leaks in JavaScript
summary
Explains how JS garbage collection actually keeps objects alive when any reference exists, demonstrates take heap snapshot and timeline comparisons in Chrome DevTools, shows a 1,000×5‑byte array example (≈5KB) and how two 5KB subarrays cause a retaining tree to keep 10KB, and points out detached DOM tree leaks. Loads a remark slideshow, profiles slide changes, finds no slide leak but identifies minified closures and orphan DOM nodes to fix.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:08What is a memory leak
- 0:53Memory in JavaScript
- 2:10How much memory is used? #3
- 4:18Key takeaways
- 6:35Leaking DOM Nodes: Part 1
- 10:22Pass only what you need
related talks
31mMemory Leaks in JavaScript
24mDemystifying Memory Leaks in JavaScript
35mAnalyze the JS Heap and detect Memory Leaks
20mMemory Leaks and the Havoc They Wreak
38mUnderstanding Memory Behavior on Nodejs
23mWarp Speed Memory Management
35mMemory Chronicles: Manage, Trace and Fix Memory Leaks
24mTrash Talk - Understanding Memory Management