Live and let die: Untangling the web of objects
summary
Chrome’s V8 and Blink interoperate via paired C++ and JavaScript object halves so DOM nodes and wrappers reference each other, leading to surprising retained graphs; the system implements cross-component tracing GC that coordinates Blink’s C++ marks with V8’s heap walk. Demo uses the DevTools heap snapshot and retaining-path view to find leaks. Concrete claims: cooperative collection reclaims DOM+JS cycles, the inspector feature just landed in Canary, and the screencast proves the workflow.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:41Disclaimer
- 2:57Java Script
- 4:55Browser
- 14:33Garbage Collection and What the Browsers Can Do for You
- 15:11Tracing Garbage Collector
related talks
24mCross-Component Garbage Collection
22mThe Hitchhiker's Guide to All Things Memory in JS
26mThe Hitchhiker's Guide to All Things Memory in Javascript
20mMemory Leaks and the Havoc They Wreak
31mJavaScript memory management: Visual Guide
19mUnderstand, find, prevent and fix memory leaks in JavaScript
23mWhat’s new in V8/JavaScript
41mBrowser Internals for JS Devs