Since memory leaks are almost always caused by arrays/objects that grow, why can't @ChromeDevTools just show those objects somewhere?
-
-
Replying to @matthewcp
you can visualize growing JS heaps / DOM nodes with the Timeline --> https://developers.google.com/web/tools/chrome-devtools/profile/memory-problems/memory-diagnosis … ^
@kaycebasques2 replies 0 retweets 0 likes -
Replying to @ChromeDevTools @kaycebasques
I do use that, but that gives me a list of all objects in memory so I have to find the growing ones.
1 reply 0 retweets 0 likes -
Replying to @matthewcp
how about allocation timelines? Do you use them / do they help? ^
@kaycebasques2 replies 0 retweets 0 likes -
Replying to @ChromeDevTools @matthewcp
got it, so you're looking for some sort of filtered list of growing objects ^
@kaycebasques2 replies 0 retweets 0 likes -
Replying to @ChromeDevTools @matthewcp
any other criteria to go off of? ^
@kaycebasques1 reply 0 retweets 0 likes -
Replying to @ChromeDevTools @kaycebasques
None that I can think of now, that would help tremendously.
1 reply 0 retweets 0 likes
thanks, I created a feature request: https://bugs.chromium.org/p/chromium/issues/detail?id=633592 … ^@kaycebasques
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.