Debugging memory leaks using @ChromeDevTools just became much easier!
Find out what’s new: https://v8project.blogspot.com/2018/03/tracing-js-dom.html …pic.twitter.com/6rPmWWLp8w
-
-
Replying to @v8js @ChromeDevTools



Is this in Canary? My stable Chrome still says v64.1 reply 0 retweets 0 likes -
Replying to @mxstbr @ChromeDevTools
It’s in Chrome 66, which is currently the Canary version.
1 reply 1 retweet 5 likes -
Will this help with node? 90% of my mem leaks come from node.js. Would love to see more example finding and fixing mem leaks with node. Great stuff regardless



2 replies 0 retweets 2 likes -
Since it's a V8 change, I imagine it would apply for Node.
@mathias will know...3 replies 0 retweets 3 likes -
Replying to @ChromeDevTools @jamischarles and
What’s described in the blog post is about V8 + DOM interaction, and is thus not relevant to Node.js.
1 reply 0 retweets 1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.