Renderer CPU usage doesn't drop for hidden full screen windows. |
||||||
Issue descriptionChrome Version: 60.0.3073.0 OS: macOS 10.12.4 What steps will reproduce the problem? (1) Open a web page that does a lot of drawing (e.g. http://listen.hatnote.com/). (2) Send the window to another space, or miniaturize it to the Dock. (3) Bring it back, then make it full screen and switch to another space (so that it's no longer visible). What is the expected result? Check the page's CPU usage with the Chrome Task Manager after each step. Its CPU usage should drop dramatically when it's not visible. What happens instead? CPU usage drops at step (2), but not at step (3).
,
Apr 21 2017
For this particular page the problem is that it is playing audio and therefore not throttled.
,
Apr 21 2017
Re. #2, minimizing the window, sending it to another desktop, or switching tabs all result in a significant drop in CPU usage. I assumed this was just a bug with full screen on Mac not setting the tab to hidden and stopping some of the rendering/compositing machinery.
,
Apr 21 2017
Re #3: Yes, you're probably right. I wonder if there is a repro without any sound played? It'll be easier to work with.
,
Apr 28 2017
Sure thing, this URI also works with the original steps:
data:text/html,<p id=count></p><script>setInterval(() => { count.textContent = +new Date(); }, 10);</script>
,
May 9 2017
altimin - mind taking this?
,
May 19 2017
,
May 19 2017
It seems that the problem is with appropriate visibility signals not being plumbed to scheduler (and blink). I'm not the best person to deal with this and I have my hands full at the moment. benhenry@, could you find someone from Chrome for Mac team to look into this?
,
May 19 2017
,
May 19 2017
I can own this, but feel free to take it.
,
Jan 26 2018
It looks like this was fixed by macOS 10.13, so I'm suspecting an issue with occlusion reporting in older OSs. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by rsch...@chromium.org
, Apr 21 2017