Investigate histogram-related CPU cost after closing a tab |
||||
Issue descriptionThis is related to https://docs.google.com/document/d/1bLWt_Eks4DYPYTthJGMNg1z8WIu4q7DqgaYqpLdm05E/edit?ts=5977880b#heading=h.wd6fm1kmrt9n We discovered that there was something histogram-related that was costing a lot of CPU. It seems like these are the repro steps. 0. start ETW tracing 1. open two tabs 2. play a video in one of the tabs for a few seconds 3. close that tab that was playing the video 4. wait a second then stop the trace 5. Notice CPU usage related to histograms toward the end of the trace. Note that if you just have the one tab open and then you close the whole browser at the end of video playback then you don't get the same result. Charliea@ was investigating this I think. Do you want to continue working on this? Let's get a clear owner.
,
Jul 26
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
,
Aug 6
Realistically, I don't have time to look into this. Closing this as WontFix - if someone else has the cycles and wants to pick it up, please do. |
||||
►
Sign in to add a comment |
||||
Comment 1 by charliea@chromium.org
, Jul 26 2017