UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2815.0 Safari/537.36
Steps to reproduce the problem:
Most leaks are caused by growing objects. Displaying some sort of simple list that just detects and lists growing objects could speed up memory leak debugging. Existing tools (Timeline memory recordings, Allocation Timelines) produce a lot of noise to weed through.
What is the expected behavior?
What went wrong?
N / A
Did this work before? No
Chrome version: 54.0.2815.0 Channel: canary
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 22.0 r0
Original discussion: https://twitter.com/matthewcp/status/760485187272802304
Comment 1 by eostroukhov@chromium.org
, Aug 2 2016Status: Assigned (was: Unconfirmed)