(In reply to Nicolas Silva [:nical] from comment #13) > Switching to EGL also appear to fix this. It's probably how we'll get this fixed in the medium/long term. (In reply to Robert Mader [:rmader] from comment #42) > You can still disable hardware acceleration by setting `gfx.webrender.software` - that should work around the issue as well. Alternatively, enabling `gfx.x11-egl.force-enabled` should work on the prop. nvidia driver as well now. Naive non-programmer question: If software 60 Hz is acceptable for software rendering and EGL, why not also for GLX? Why wasting time on it? Could GLX_SGI_video_sync be put behind an `(isMesa || StaticPrefs::gfx_vsync_glx_nonmesa_AtStartup())` check to unship this bug? Then we could focus on enabling MOZ_X11_EGL (bug 1695933) and GPU process (might not get correct visual: bug 1654658 comment 11).
Bug 1716049 Comment 44 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 Nicolas Silva [:nical] from comment #13) > Switching to EGL also appear to fix this. It's probably how we'll get this fixed in the medium/long term. (In reply to Robert Mader [:rmader] from comment #42) > You can still disable hardware acceleration by setting `gfx.webrender.software` - that should work around the issue as well. Alternatively, enabling `gfx.x11-egl.force-enabled` should work on the prop. nvidia driver as well now. Naive non-programmer question: If software 60 Hz is acceptable for software rendering and EGL, why not also for GLX? Why wasting time on it? Could GLX_SGI_video_sync be put behind an `(isMesa || StaticPrefs::gfx_vsync_glx_nonmesa_AtStartup())` check to unship this bug? Could this work? Then we could focus on enabling MOZ_X11_EGL (bug 1695933) and GPU process (might not get correct visual: bug 1654658 comment 11).
(In reply to Nicolas Silva [:nical] from comment #13) > Switching to EGL also appear to fix this. It's probably how we'll get this fixed in the medium/long term. (In reply to Robert Mader [:rmader] from comment #42) > You can still disable hardware acceleration by setting `gfx.webrender.software` - that should work around the issue as well. Alternatively, enabling `gfx.x11-egl.force-enabled` should work on the prop. nvidia driver as well now. Naive non-programmer question: If software 60 Hz is acceptable for software rendering and EGL, why not also for GLX? Why wasting time on it? Could GLX_SGI_video_sync be put behind an `(isMesa || StaticPrefs::gfx_vsync_glx_nonmesa_AtStartup())` check to unship this bug? Could this work? Then we could focus on enabling MOZ_X11_EGL (bug 1695933) and GPU process (might not get correct visual: bug 1654658 comment 11).
(In reply to Nicolas Silva [:nical] from comment #13) > Switching to EGL also appear to fix this. It's probably how we'll get this fixed in the medium/long term. (In reply to Robert Mader [:rmader] from comment #42) > You can still disable hardware acceleration by setting `gfx.webrender.software` - that should work around the issue as well. Alternatively, enabling `gfx.x11-egl.force-enabled` should work on the prop. nvidia driver as well now. Naive non-programmer question: If software 60 Hz is acceptable for software rendering and EGL/Nvidia, why not also for GLX? Why wasting time on it? Could GLX_SGI_video_sync be put behind an `(isMesa || StaticPrefs::gfx_vsync_glx_nonmesa_AtStartup())` check to unship this bug? Could this work? Then we could focus on enabling MOZ_X11_EGL (bug 1695933) and GPU process (might not get correct visual: bug 1654658 comment 11).