Addy Osmani originally shared this post:
To help discover these leaks, two of my fellow Googlers (and ) have developed a tool that works with the Chrome Developer Tools (specifically, the remote inspection protocol) and retrieves heap snapshots and detects what objects are causing leaks.
Some more info: In case you're wondering why a tool like this isn't already integrated with our Developer Tools, the reason is two fold. It was originally developed to help us catch some specific memory scenarios in the Closure Library and it makes more sense as an external tool (or maybe even an extension if we get a heap profiling extension API in place).
News about Google"s Open Source projects and programs
A simple & sensible blueprint!
“A conference on ECMA-262” doesn’t sound particularly exciting, so I can understand the organisers of Full Frontal 2009 wanting to pick a name that was perhaps more attention grabbing. I’m heading along there tomorrow, and depending on the format (& facilities at my disposal) I’ll hopefully be able to blog and tweet throughout.