Something is wrong with #Mozilla #Firefox 116 b8 under #PopOS 22.04.
It keeps hanging, or crashing, when there are #JavaScript interactions.
What I’ve tried:
* Uninstall Firefox
* Delete all profiles
* Delete all cache
* Reboot
* Install Firefox
* Test from a fresh installation, Without any customizations and addons/extensions.
* Disabled HTTP3 (which was the issue for a similar case a year ago).
* No, I don’t have popcorntime installed (which is/was an issue for #Wayland.)
* I’m using #X11 not Wayland.
Other information:
* I can’t even login to #Google. After entering my password, the tab just stops working. It stops interacting. No clicks, no tabbing, no arrow cursor.
* I can’t event open about:support it hangs.
* I can’t use #Facebook, eventually the tab will stop interacting. No clicks, no tabbing, no arrow cursor.
* I can’t watch videos on #YouTube. If the YT ads play first, it will get stuck there. If the actual video plays first, after a few seconds it will either get stuck at some frame, or just keep playing without any interaction (can’t stop, etc.)
My device:
* Pop!_OS 22.04 which is #Ubuntu / #Debian based.
This is totally out of my league. I don’t know what else to test.
So, I switched to #Naver #Whale as my primary #browser for now. It is a #Chromium-based browser from #Korea.
Oh, one more thing, when I close Firefox, it pops-up an error that it crashed. Since the 116b8 update, Firefox just kept on crashing when closing.
#Linux #bugs #bug #support #YourOnlyOne #techmagus
@youronlyone@firefish.social @Linux@chirp.social @linux@lemmy.ml
@youronlyone@c.im @youronlyone@firefish.social @Linux@chirp.social @linux@lemmy.ml Have you tried to run it from the terminal to see what errors pop out?
Good question! Forgot that.
Just tested it with
--safe-modeflag and everything works fine.Without the flag… found the culprit. See attached file.
@youronlyone@firefish.social @Linux@chirp.social @linux@lemmy.ml
@youronlyone@c.im @youronlyone@firefish.social @Linux@chirp.social @linux@lemmy.ml hmm. Usually when mesa errors are happening it’s a driver issue, but I’ve never seen it effect just one app before.
You could try Firefox-ESR.
@youronlyone@c.im @thelinuxcast @youronlyone@firefish.social @Linux@chirp.social @linux@lemmy.ml
How about if you go into settings, uncheck “Use recommended performance settings” and then uncheck “Use hardware acceleration when available”?
Tried that, and the hang-up / crash took longer before it happened.
I guess there’s a libEGL / X11 / FF combination that is no longer working fine with 116 b8.
When I enabled Wayland in Pop_OS 22.04 and switched to it, FF 116 b8 started to work smoothly. Though with hardware acceleration enabled under Wayland.
@thelinuxcast @youronlyone@firefish.social @Linux@chirp.social @linux@lemmy.ml
@youronlyone@c.im @thelinuxcast @youronlyone@firefish.social @Linux@chirp.social @linux@lemmy.ml
Ah, all right. Figured it was worth a try, in case the hardware acceleration was the issue…
