Is this in Canary? My stable Chrome still says v64.
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
-
-
-
It’s in Chrome 66, which is currently the Canary version.
- 4 more replies
New conversation -
-
-
Awesome!
-
Only issues I see is that this removes some of my job security :troll:
End of conversation
New conversation -
-
-
what happened to the "detached dom nodes" in snapshots, should they show up under "Leaks"?
-
digging into this example https://github.com/travis-hilterbrand/js-memory-leaks-demos/blob/master/demo-3.html … (via
@pixel_grid) I managed to find the detached node under the window object under containment - 5 more replies
New conversation -
-
-
can you get this fixed in Canary? it sucks being a developer down under :) https://bugs.chromium.org/p/chromium/issues/detail?id=814100 … (sorry for the topic fucking)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I love this!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Trying the feature in this demo repo for finding memory leaks and searching for Leak returns nothing.https://github.com/travis-hilterbrand/js-memory-leaks-demos …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Love y'all
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.