Potential memory leak with UKM and scrolling |
|||
Issue descriptionI'm running a canary version for about 5 days with native heap profiling enable. I'm collecting traces every day and watching for allocated objects remaining alive. The stackframe attached to the bug are probably related to a potential memory leak. I can't tell if the number of objects is possible. Could you please look over my shoulders.
,
Aug 1 2017
Assigning to Navid for triage.
,
Oct 24 2017
I need a little more information regarding how to read the image. But I don't see any difference the way we used ukm compared to the other occurrences. holte@ do we need to do any cleanup regarding the builders or examples or anything like that here: https://cs.chromium.org/chromium/src/content/browser/renderer_host/input/render_widget_host_latency_tracker.cc?type=cs&sq=package:chromium&l=436
,
Oct 24 2017
I didn't saw that bug happening since a while. We have better tracking tools now, I'm gonna come back pinging you in this bug if this is still happening. For the metrics in the image it is: 1) number of allocation still alive 2) total number of bytes allocated 3) the specific allocation stack frame
,
Oct 24 2017
Alright then. Let's keep this closed. Feel free to open this if you see the same thing happening again. Thanks. |
|||
►
Sign in to add a comment |
|||
Comment 1 by privard@chromium.org
, Aug 1 2017