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
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
-
-
also the leaking elements are flagged red in stable but not in canary, if that's restored in canary, have you considered the option of marking the top level node red if any of the child nodes are leaks? (tortoiseGit has this option for folders containing modified files)
-
I've been thinking how to show leaks and memory issues (e.g. duplicate strings) that DevTools can detect programmatically. I'm in favor of having a separate view that lists all these issues. Highlighting parents as red is an interesting idea. I'll bring it up in the next meeting
- Još 3 druga odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.