Firefox crashing after egl-wayland upgrade (on nvidia)

Feedback Bugreports
1

After the latest egl-wayland upgrade, it appears as though Firefox (including the Cachy Browser) is once again crashing when running on nvidia/wayland:

upgraded egl-wayland (2:1.1.13-3 -> 2:1.1.14-1.1)
upgraded linux-cachyos (6.10.0-2 -> 6.10.0-3)
upgraded linux-cachyos-headers (6.10.0-2 -> 6.10.0-3)
upgraded linux-cachyos-nvidia (6.10.0-2 -> 6.10.0-3)

[4][GFX1-]: Wayland protocol error: wp_linux_drm_syncobj_surface_v1#83: error 4: explicit sync is used, but no acquire point is set
Exiting due to channel error.

If I’m not mistaken a patch was added to specifically counter this issue when the 555 driver was just released, but unfortunately it does not seem to be active/working after these latest upgrades?

2

I have requested at archlinux to apply patches for firefox.
see: Add fixes for egl-wayland explicit sync patches (#7) · Issues · Arch Linux / Packaging / Packages / firefox · GitLab
Heftig, the maintainer of firefox has assigned it. So lets see if he puts them.

Meanwhile - use cachy-browser. It includes the patches.

3

egl-wayland got a release, which included explicit sync for egl windows.

Since Firefox does violate the protocol, because its dirty written it does crash.

4

Thanks for the info. Unfortunately, cachy-browser is also crashing since these latest upgrades (the logs in my post are from cachy-browser crashing).

5

Please update to 128.0-3 as version.

6

Not seeing the 128.0-3 release yet, will upgrade as soon as it presents itself. Thanks.

7

Some mirrors have 1 hour delay, since not hosted by us. Maybe you got one of them :slight_smile:

8

Yep, upgrade came through and it’s usable again. Although it did crash once in a similar way since upgrading, hopefully just a fluke.

9

It seems the crash was not a fluke, and it happens occasionally on 128.0-3 (much less than the egl-related crashes though):

[Parent 42719, Compositor] WARNING: Call to mmap failed: Bad file descriptor: file /usr/src/debug/cachy-browser/firefox-128.0/ipc/chromium/src/base/shared_memory_posix.cc:515
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
fish: Job 1, 'cachy-browser' terminated by signal SIGSEGV (Address boundary error)
10

Yes, Firefox upstream issue still discussing. With these patches its fine from their side, and its an issue in mesa.

You can workaround it with MOZ_ENABLE_WAYLAND=0 cachy-browser

3 Likes