How useful is it when @ChromeDevTools gets unresponsive when I run into a memory-leak? I think is due to the shared process resources.
DevTools should pause before the page crashes the browser:https://developers.google.com/web/updates/2017/03/devtools-release-notes#out-of-memory-breakpoints …
-
-
That's the case but during the memory increase I can't profile the app. The devTools feel very unresponsive and a heap snapshot or perf analyse runs forever until that message about a detected memory leak appears. Any tips?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
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.