In hope for better memory tools
summary
Browser heaps use mark-and-sweep roots and reachability, and Chrome’s heap snapshot groups objects by constructor and produces noisy tables full of transient allocations and wasted whitespace. The concrete complaint is that snapshots don’t map to source code, don’t highlight surviving objects, and drown useful information in deltas. A prototype builds a live in-page graph visualization of the runtime to show actual retained objects and edges so investigation finds the real leak locations.
AI-written summary · about
chapters (4)
related talks
53mPlugging Memory Leaks With The Chrome Dev Tools
47mUntangling the web: Memory management in Chrome’s web platform implementation
20mMemory Leaks and the Havoc They Wreak
35mMemory Chronicles: Manage, Trace and Fix Memory Leaks
23mWarp Speed Memory Management
31mMemory Leaks in JavaScript
19mUnderstand, find, prevent and fix memory leaks in JavaScript
22mThe Hitchhiker's Guide to All Things Memory in JS