Your App Crashes My Browser
summary
Claims that single‑page apps commonly leak memory — Nolan Lawson’s scan finds 10 out of 10 popular SPAs leaking and one case shows 186 MB after a single interaction. Uses the Reporting API to collect real out‑of‑memory events, MemLab (Facebook) plus a Chrome recorder extension (50 users) to run Puppeteer scenarios, take GC snapshots and diff them; typical fixes are unmount/cleanup of event listeners, clearing intervals, and removing console‑retained references.
AI-written summary · about
chapters (10)
- 0:00Introduction to React and JavaScript Leaks
- 1:44Memory Leaks and Tools for Fixing Them
- 3:07Addressing Memory Leaks with the Reporting API
- 4:44Debugging and Memory Snapshots with Memlab
- 6:43Using Memlab for Memory Leak Detection
- 8:02Fixing Memory Leaks and Common Patterns
- 9:53Spotting and Fixing Leaks in React Components
- 12:11Unmounting and Cleanup in React
- 13:51Plugging Leaks and Final Remarks
- 15:50Web Performance and Memory Leaks
related talks
06mYour app crashes my browser
31mMemory Leaks in JavaScript
20mMemory Leaks and the Havoc They Wreak
24mDemystifying Memory Leaks in JavaScript
53mPlugging Memory Leaks With The Chrome Dev Tools
23mWarp Speed Memory Management
35mMemory Chronicles: Manage, Trace and Fix Memory Leaks
27mTwo memory leak stories in the story of flipkart.com