The Memory Leak Brain Drain – Workshop
summary
A practical walkthrough of chasing browser leaks: reproduces a contrived counter that creates an array of 10,000 items and a polling observable that never unsubscribes, shows memory climbing in Chrome DevTools timeline, isolates retaining objects with the allocation timeline and heap snapshots, explains minor vs major GC: 1–25ms vs 30ms+ and why detached DOM trees long-lived subscriptions and console logging hold references, then fixes it by unsubscribing and adding an explicit stopPulling call so the retained nodes and heap growth disappear.
AI-written summary · about
chapters (17)
- 0:00Start
- 0:38Large scale memory leaks
- 2:32What is a memory leak?
- 9:35Garbage Collection Takeaways
- 9:51Types of Memory Management
- 10:18Manual Memory Management
- 10:50Reference Counting
- 11:43Javascript Engines
- 12:44A user using your app
- 13:52Minor GC happens again
- 14:34Minor Garbage Collections
- 16:32Single Threaded Browser
- 17:01Observational signs of a memory leak
- 19:43Detached DOM Trees
- 20:33Long lived observables
- 21:18Console API
- 35:09Conclusion
related talks
06mYour app crashes my browser
27mTwo memory leak stories in the story of flipkart.com
31mAdvanced Memory Debugging with Xcode Tools
40mClient Side MVC and The Gosh Darn Back Button
29mWatch your back, Browser! You're being observed
17mVisualising Front-End Performance Bottlenecks
27mAnd Benchmarks for All!
41m10 things you didn't know a browser could do