Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Firefox on Linux freezing with 5-8 tabs open

  • 2 antwurd
  • 0 hawwe dit probleem
  • 1 werjefte
  • Lêste antwurd fan zeroknight

more options

I am running Firefox 122.0 on Ubuntu 22.04. When I have a decent number of tabs open, firefox will often randomly decide to lock up completely. GUI is almost entirely unresponsive. I can right click the menu bar area and get the Menu Bar/Bookmark Options/etc. context menu, but it's also screwed up (2 options that are normally there are completely missing). This has occurred for a year or so. Originally, I used the snap version but recently backed up and switched to installing from .deb. Still the same issue. I saw recommendations for turning off hardware acceleration, and that didn't prevent the problem. Running `top`, I see that I always have plenty of memory (at least 10G free) free and worst case 1 thread is being run 100% but the others are hardly being utilized. No crash reports are generated (I will pkill firefox to stop it). Addons and extensions are all disabled.

I recently realized that hitting the windows key with firefox frozen will allow the web page to show again, but it's back to frozen. I keep hitting the windows key, and it will unfreeze just momentarily to show me the current webpage that is up. I can also Ctrl+N and open a new window, and the new window works perfectly fine independent of the completely frozen first window.

I am running Firefox 122.0 on Ubuntu 22.04. When I have a decent number of tabs open, firefox will often randomly decide to lock up completely. GUI is almost entirely unresponsive. I can right click the menu bar area and get the Menu Bar/Bookmark Options/etc. context menu, but it's also screwed up (2 options that are normally there are completely missing). This has occurred for a year or so. Originally, I used the snap version but recently backed up and switched to installing from .deb. Still the same issue. I saw recommendations for turning off hardware acceleration, and that didn't prevent the problem. Running `top`, I see that I always have plenty of memory (at least 10G free) free and worst case 1 thread is being run 100% but the others are hardly being utilized. No crash reports are generated (I will pkill firefox to stop it). Addons and extensions are all disabled. I recently realized that hitting the windows key with firefox frozen will allow the web page to show again, but it's back to frozen. I keep hitting the windows key, and it will unfreeze just momentarily to show me the current webpage that is up. I can also Ctrl+N and open a new window, and the new window works perfectly fine independent of the completely frozen first window.

Bewurke troch veto1024 op

Alle antwurden (2)

more options

Did you tried Firefox in Safe Mode? https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode#search Did you try downloading Firefox from Mozilla? Download, unzip, and run firefox-bin from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release What Desktop? X11 or Wayland?


Operating System: openSUSE Tumbleweed 20240126 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.7.1-2-default (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz Memory: 125.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: HP Product Name: HP ZBook 17 G6

more options

If you use Developer Edition (early beta), you can recover from this situation by clicking the "Trigger Device Reset" button in about:support (when the problem occurs, the label is "gpu-device-reset" and the button is "undefined").