Firefox crashes with Explicit Sync enabled in Wayland
Affected version
OS - Arch-testing Mutter - 46.2 Only Wayland impacted (with Firefox running in Wayland mode) Nvidia 555 series drivers required (for explicit sync support)
Bug summary
When launching Firefox in Wayland mode (default nowadays, at least with Nightly/beta, probably stable too), on the latest Mutter release with Nvidia 555 series drivers, Firefox crashes very quickly on most web pages. about:support
and some internal pages seem fine. The error message printed in console is from mutter, however, not Firefox, leading me to report it here.
Steps to reproduce
- Install Nvidia 555 series drivers on a system with Nvidia graphics as primary display (NOT Prime, Nvidia must be in use for the compositor)
- Launch a Gnome Wayland session
- Launch Firefox with MOZ_ENABLE_WAYLAND=1 (default), visit google.com (or many other pages reproduce)
Setting MOZ_ENABLE_WAYLAND=0 or running a Xorg session works around this.
What happened
Firefox crashes
What did you expect to happen
Firefox to run
Relevant logs, screenshots, screencasts etc.
$ firefox-nightly/firefox
[GFX1-]: Wayland protocol error: wp_linux_drm_syncobj_surface_v1@59: error 4: No Acquire point provided
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
ExceptionHandler::GenerateDump cloned child 43927
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
This error printout does not exist in Firefox code, I think it's coming from: https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/wayland/meta-wayland-linux-drm-syncobj.c#L614
I also reported this to Mozilla here: https://bugzilla.mozilla.org/show_bug.cgi?id=1898476 And there was a similar bug+fix impacting a KDE video playback application from another user with Radeon here: https://invent.kde.org/plasma/kwin/-/merge_requests/5683