Since memory leaks are almost always caused by arrays/objects that grow, why can't @ChromeDevTools just show those objects somewhere?
you can visualize growing JS heaps / DOM nodes with the Timeline --> https://developers.google.com/web/tools/chrome-devtools/profile/memory-problems/memory-diagnosis … ^@kaycebasques
-
-
I do use that, but that gives me a list of all objects in memory so I have to find the growing ones.
-
how about allocation timelines? Do you use them / do they help? ^
@kaycebasques - 1 more reply
New conversation -
-
-
The "finding" is the hard part. A simple list of arrays whose .length has increased over a time would be great
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.