Since memory leaks are almost always caused by arrays/objects that grow, why can't @ChromeDevTools just show those objects somewhere?
how about allocation timelines? Do you use them / do they help? ^@kaycebasques
-
-
They help a little, but typically there are a LOT of new allocations, still have to weed through a long list.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
got it, so you're looking for some sort of filtered list of growing objects ^
@kaycebasques -
Yes, exactly! That is the source of most leaks I've ran into.
End of conversation
New conversation -
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.