User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:107.0) Gecko/20100101 Firefox/107.0

Steps to reproduce:

Launch Firefox

Actual results:

The process is executed but no window is created, multiple processes can be started in this state. Sending SIGTERM to one of the child processes causes it to stop hanging but which child it is seems to vary somewhat.

Expected results:

A window should have been created, either the main window or a window complaining that Firefox is running but unresponsive.

Some additional information:

• I'm experiencing this on Void Linux
• The Void build (but not the Mozilla build) complains about JavaScript error: resource://gre/modules/XULStore.jsm, line 58: Error: Can't find profile directory. (which is resolved: https://bugzilla.mozilla.org/show_bug.cgi?id=1548017) (I don't know how to do the nice bug links)
• Sometimes working around the bug by killing the child process will cause it to be fixed until I reboot

(In reply to Sethhphillips from comment #2)

Some additional information:

Also, the traces were both captured as follows:

1. launch 1 or more Firefox instances (they all get stuck in this state)
2. run strace -ff -ttt -s256 --decode-fds=all -ofirefox.trace firefox
3. wait a few seconds to make sure it's hung
4. send SIGTERM to the correct child process (guessing based on how the processes & threads get laid out in htop's tree view)
5. dismiss window complaining that Firefox is running but unresponsive.

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

I recently noticed that immediately after receiving SIGTERM Firefox prints this message on STDOUT:
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: VA-API test failed: process crashed. Please check your VA-API drivers. (t=13.0441) [GFX1-]: glxtest: VA-API test failed: process crashed. Please check your VA-API drivers.
(all on one line, as presented here)

However my VA-API drivers appear to be fine:

$ vainfo
libva info: VA-API version 1.16.0
libva info: Trying to open /usr/lib64/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_1_16
libva info: va_openDriver() returns 0
Trying display: wayland
vainfo: VA-API version: 1.16 (libva 2.16.0)
vainfo: Driver version: Mesa Gallium driver 22.2.4 for VERDE (, LLVM 12.0.1, DRM 2.50, 6.0.15_1)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileNone                   :	VAEntrypointVideoProc

Please check if downgrading to libx11 1.8.1 avoids the problem. Void Linux upgraded to 1.8.2 on 2022-11-11 (bug 1801820).

(In reply to Darkspirit from comment #6)

Please check if downgrading to libx11 1.8.1 avoids the problem. Void Linux upgraded to 1.8.2 on 2022-11-11 (bug 1801820).

Unfortunately the problem still occurs with libX11 downgraded to 1.8.1

VA-API test failed: process crashed.

Do you have deprecated libva-vdpau-driver installed? It doesn't support vaGetDisplayDRM and would crash. Does the problem still occur after removing it (in case you have it)?

(In reply to Darkspirit from comment #8)

VA-API test failed: process crashed.

Do you have deprecated libva-vdpau-driver installed? It doesn't support vaGetDisplayDRM and would crash. Does the problem still occur after removing it (in case you have it)?

I don't have libva-vdpau-driver installed, here's a list of the libva and vdpau packages I do have installed if it'll help:

libva-2.16.0_1
libva-32bit-2.16.0_1
libva-utils-2.16.0_1
libvdpau-1.5_1
libvdpau-32bit-1.5_1
mesa-vdpau-22.2.4_2
mesa-vdpau-32bit-22.2.4_2

I replaced my graphics card (Radeon HD 7750 using the radeon kernel driver) with a slightly newer one (Radeon Pro WX2100 using the amdgpu kernel driver) and this bug went away so it seems this hang has something to do with how the radeon driver handles vaapi.
I still have the previous card but I suspect this hang may just be the result of something having been misconfigured otherwise there would probably be more people experiencing it.
Should I close this bug, or should I wait a bit to see if someone else has the same issue?
Alternatively, I could put the card back in for a bit if you have any suspicions about the source of this bug?

Dupe of Bug 1787182.