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
-
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
Since it's a V8 change, I imagine it would apply for Node. @mathias will know...
-
-
What’s described in the blog post is about V8 + DOM interaction, and is thus not relevant to Node.js.
-
Shows how much I know! --- Kayce
End of conversation
New conversation -
-
-
That is why chrome is the Dev choice I can't say others are even close in matching it. Well except
@firefox for WebRTC. Otherwise you guys dominate.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
+1 this would be amazing for Node... I've had to debug so many memory leaks with just about every Node project I've worked on.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.