1732582 - [snap] Tab crash on first run assumingly on about:welcome: Crash in [@ libxkbcommon.so.0@0x1ae24]

Status: RESOLVED DUPLICATE of bug 1732580

(Release Engineering :: Release Automation: Snap, defect)

Description

[Darkspirit]

Attachment: aboutsupport.txt

Gnome Wayland, Debian Testing, Intel

(Darkspirit from bug 1726510 comment 36)

$ sudo snap remove firefox
$ sudo snap install firefox
$ snap run firefox

WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement
xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb

First startup: Tab crash assumingly on about:welcome:
bp-e7d043e2-3b16-4677-8810-fdfa80210926 [@ libxkbcommon.so.0@0x1ae24 ]

Crash report: bp-e7d043e2-3b16-4677-8810-fdfa80210926

Reason: SIGSEGV / SEGV_MAPERR

Top 10 frames of crashing thread:

0 libxkbcommon.so.0 libxkbcommon.so.0@0x1ae24 
1 libxkbcommon.so.0 libxkbcommon.so.0@0x1cfdb 
2 libxkbcommon.so.0 libxkbcommon.so.0@0x40d9f 
3 libxkbcommon.so.0 libxkbcommon.so.0@0x1c8f9 
4 libgdk-3.so.0 libgdk-3.so.0@0x7bfe8 
5 libgdk-3.so.0 libgdk-3.so.0@0x7202a 
6 libffi.so.7 libffi.so.7@0x92f3 
7 libffi.so.7 libffi.so.7@0x8434 
8 libffi.so.7 libffi.so.7@0x68bb 
9 libgdk-3.so.0 libgdk-3.so.0@0x71fef 

Comment 1

[Alex Bennée]

I'm seeing regular crashes of tabs (seemingly at random). My tracebacks also include libxkbcommon and I'm running Wayland which makes me wonder if that is the common issue. Will the libxkbcommon be using the system library or be part of the core snap overlays?

Comment 2

[Alex Bennée]

Moving from the snap to the flatpak (92.0.1) and the I've had a whole day without any crashes. Looking at about:support it lists the rendering engine as xwayland (instead of wayland). I can also run the WebGL demos again so it looks like it's the pure wayland support that is busted. Is there a meta-bug for Wayland issues?

Comment 3

[Darkspirit]

(In reply to Alex Bennée from comment #2)

Moving from the snap to the flatpak (92.0.1) and the I've had a whole day without any crashes. Looking at about:support it lists the rendering engine as xwayland (instead of wayland).

Is there a meta-bug for Wayland issues?

bug 635134 and bug 1543600 are for pre-Nightly MOZ_ENABLE_WAYLAND=1. That's when window protocol is wayland on about:support.
I haven't seen a bug report like this for official Mozilla binaries.

I can also run the WebGL demos again so it looks like it's the pure wayland support that is busted.

Offtopic (bug 1732580):
No, you mix different aspects. "EGL in Snap" is the cause, not Wayland.
MOZ_ENABLE_WAYLAND=1 enforces Firefox' experimental Wayland backend which requires EGL.
Firefox 92 Snap uses pre-Nightly MOZ_ENABLE_WAYLAND by default.
Firefox 92 uses GLX by default on Xwayland and X11.
As of 94 (bug 1695933), Mesa 21 users will use EGL on Xwayland and X11 as well. That made it possible to enable hardware rendering on Xwayland. (bug 1730671, bug 1635186 comment 49). The Snap WebGL bug can also be reproduced with Firefox 92 Snap on xwayland (DISABLE_WAYLAND=1 env var) and x11 when setting gfx.x11-egl.force-enabled=true and restarting Firefox.

Comment 4

[Chris Peterson [:cpeterson]]

Seems like this is an external change affecting Firefox because:

• The crash reports spiked on both the Release and Beta channels around 2021-09-26.
• All but 5 (0.3%) of the crash reports are from some version of Ubuntu (17, 18, 20, 21, dev).