Sure enough, if you disable unredirection as described here:įrom what I'm reading, it sounds like the application ends up being responsible for handling vsync to avoid tearing when it's not redirected through the compositor. When you hit the key again to go back to full screen, it starts tearing again immediately.
If you hit the Windows key to open the overview, which zooms down the video into a frame (presumably forcing it to be redirected again), the tearing stops. When you open a full-screen video for the first time after opening the browser, after a few seconds (probably when 100 frames have been played), suddenly the video starts tearing. If that happens, then the window should be unredirected." Games (or SDL2) don't set the recently added _NET_WM_BYPASS_COMPOSITOR hint, so we fall back to heuristics: a non-ARGB32 full-screen / monitor-sized window that does 100 full-screen redraws in a row.
"GNOME 3 automatically unredirects some full-screen windows.
After looking into this a bit more, it sounds like mutter (the GNOME3 compositor) has a heuristic that it uses to detect when it should unredirect the window.
0 kommentar(er)
