(In reply to Sotaro Ikeda [:sotaro] from comment #64) > I wonder if window occlusion throttling stopped to work correctly at some point. It might be around WinWindowOcclusionTracker or [AppWindow::OcclusionStateChanged()](https://searchfox.org/mozilla-central/rev/9c395b6371eaea0d15f9c8a37889022be350cf0b/xpfe/appshell/AppWindow.cpp#2804) does not work as expected. I looked into if AppWindow::OcclusionStateChanged() is handled as expected in gecko. With the following STR, there is a case that nsRefreshDriver continued to tick with VsyncRefreshDriverTimer and Vsync keeps running. It seemed like a problem. - [1] Start Firefox - [2] Move to https://www.youtube.com/watch?v=LXb3EKWsInQ - [3] Start video playback - [4] Move the Firefox window to be occluded by other app window
Bug 1924932 Comment 67 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Sotaro Ikeda [:sotaro] from comment #64) > I wonder if window occlusion throttling stopped to work correctly at some point. It might be around WinWindowOcclusionTracker or [AppWindow::OcclusionStateChanged()](https://searchfox.org/mozilla-central/rev/9c395b6371eaea0d15f9c8a37889022be350cf0b/xpfe/appshell/AppWindow.cpp#2804) does not work as expected. I looked into if AppWindow::OcclusionStateChanged() is handled as expected in gecko. With the following STR, there were cases that nsRefreshDriver continued to tick with VsyncRefreshDriverTimer and Vsync keeps running. It seemed like a problem. - [1] Start Firefox - [2] Move to https://www.youtube.com/watch?v=LXb3EKWsInQ - [3] Start video playback - [4] Move the Firefox window to be occluded by other app window