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

Steps to reproduce:

1. Enable hardware acceleration when available
2. Open the downloads window (with the menu or with the shortcut Ctrl + Shift + Y)

Sometimes I have to repeat the second step 2-3 times for the bug to happen, but generally speaking I only need to do it once.

At first it looks like making a new profile gets rid of the issue, but after a few attempts the problem starts to happen in the new one. The only thing I've done is switch between profiles, change the default one and constantly open the downloads window.

Creating a new window allows me to sometimes open the downloads window once, but if I try to close it and open it again the issue happens again.

Other things that have no effect:

• Starting firefox on troubleshooting mode
• The number of tabs or websites I am visiting
• Changing the downloads folder
• Clearing Cookies and Site Data
• Reinstalling firefox
• Using an older version of firefox (107.0.1-1 -> 106.0.1-1)

Important things to note about my setup:
OS: Arch Linux x86_64
Kernel: 6.0.10-arch2-1
Shell: zsh 5.9
Resolution: 1920x1080, 1920x1080
- I use 2 displays on the "joined" configuration
DE: Gnome 43.1
WM: Mutter
CPU: Intel i7-9750H (12) @ 4.500GHz
GPU: NVIDIA GeForce GTX 1660 Ti Mobile
GPU: Intel CoffeeLake-H GT2 [UHD Graphics 630]
Memory: 2314MiB / 15847MiB
Nvidia drivers: 525.60.11-1 (the latest at the time of writing)
Firefox version: 107.0.1-1

Nvidia laptop, with optimus-manager on NVIDIA mode. The issue DOES NOT happen if I switch to only using integrated or hybrid graphics.

Please do note that when running on hybrid and trying to launch firefox with
prime-run, it doesn't actually use the graphics card, I checked on about:support under the "Graphics" section, and the Compositing row listed "WebRender (Software)"

The console yields the following message when trying to use prime-run firefox:

[GFX1-]: glxtest: VA-API test failed: process crashed. Please check your VA-API drivers.
[GFX1-]: Failed to create EGLSurface!: 0x3009
[GFX1-]: Failed to create EGLSurface. 1 renderers, 0 active.
[GFX1-]: Handling webrender error 3
[GFX1-]: Fallback WR to SW-WR
[2022-12-01T15:26:33Z ERROR glean_core::metrics::ping] Invalid reason code startup for ping background-update

Actual results:

Firefox window would then proceed to freeze and be completely unresponsive. No animations would play. If I was watching a youtube video, the audio would continue to play for a few seconds before stopping. Afterwards, a small window would appear with the following text:

"Firefox" is not responding.

You may choose to wait a short while for it to continue or force the application to quit entirely.

[Force Quit] [Wait]

If I select wait, the warning will disappear for a few seconds, but the windows will still be unresponsive, just for the warning to appear again.

If multiple windows are open, the freeze affects all of them

Expected results:

The Downloads window opens, displaying my downloaded files and allowing me to manage them, without making firefox 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.

(In reply to Release mgmt bot [:suhaib / :marco/ :calixte] from comment #1)

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.

Corrected the following things:
Product: Firefox
Component: Downloads Panel
Version: Firefox 107
Platform: Desktop (Linux)

• Please attach about:support page
• Please test latest nightly
  https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_Mozilla_binaries
  Thanks.

about:support page contents

(In reply to Martin Stránský [:stransky] (ni? me) from comment #3)

• Please attach about:support page
• Please test latest nightly
  https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_Mozilla_binaries
  Thanks.

Greetings! I've installed nightly through this link.

I unpacked the tarball on ~/.local/firefox-nightly and created a new profile called "nightly-testing", and downloaded a few files. The download's manager seemed to open just fine, but after switching to my regular profile it would hang. Not only that, the issue seems to have propagated to the new "nightly-testing" profile.

A new issue I've also noticed is that I don't even need to switch back and forth between profiles for the bug to happen, I can create a new fresh profile, download a file, delete it on the file manager, and when I try to open the download manager it hangs. This issue happens on both firefox 107 and nightly.

I should add that the bug doesn't happen in nightly if I have hardware acceleration disabled.

I see you use KDE/X11.

Please try to attach crash ID of the frozen Firefox Nightly:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Getting_Mozilla_crash_report_from_running_or_frozen_Firefox
Thanks.

(In reply to Martin Stránský [:stransky] (ni? me) from comment #7)

I see you use KDE/X11.

Please try to attach crash ID of the frozen Firefox Nightly:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Getting_Mozilla_crash_report_from_running_or_frozen_Firefox
Thanks.

Not KDE, Gnome.

This is the crash report:
https://crash-stats.mozilla.org/report/index/c153093d-7395-49f9-9b38-e0f4f0221208

Sorry, I don't think that was the crash report for nightly. This is one for nightly done on a fresh profile:
https://crash-stats.mozilla.org/report/index/83a79ead-998a-4519-bc7e-bf2f90221208

Issue persists in the current nightly build (Mozilla Firefox 110.0a1):
https://crash-stats.mozilla.org/report/index/651c97ae-1ff7-4c8c-a444-3c40f0221215

And on the newest stable arch linux release (Mozilla Firefox 108.0):
https://crash-stats.mozilla.org/report/index/0b74ce59-9b0b-477f-8303-1178f0221215

(In reply to SPARTAN643 from comment #10)

Issue persists in the current nightly build (Mozilla Firefox 110.0a1):
https://crash-stats.mozilla.org/report/index/651c97ae-1ff7-4c8c-a444-3c40f0221215

Thanks!
[@ futex_wait ] is Nvidia-only and ArchLinux/EndeavourOS-only.
First occurences: 2022-11-14 (106.0.5), 2022-11-17 (107.0), 2022-11-25 (109.0a1).

bug 1802229 comment 6 says this commit of libx11 1.8.2 caused a regression that hit Arch linux users.

(In reply to Darkspirit from comment #11)

(In reply to SPARTAN643 from comment #10)

Issue persists in the current nightly build (Mozilla Firefox 110.0a1):
https://crash-stats.mozilla.org/report/index/651c97ae-1ff7-4c8c-a444-3c40f0221215

Thanks!
[@ futex_wait ] is Nvidia-only and ArchLinux/EndeavourOS-only.
First occurences: 2022-11-14 (106.0.5), 2022-11-17 (107.0), 2022-11-25 (109.0a1).

bug 1802229 comment 6 says this commit of libx11 1.8.2 caused a regression that hit Arch linux users.

*** This bug has been marked as a duplicate of bug 1802229 ***

It seems like that's the case. Haven't tried out the AUR patch just yet, but downgrading to libx11 1.8.1-3 seems to fix the issue. Thanks a lot for the help!

bug 1801820 created the Arch Linux ticket.