You are not logged in.
Ive been using Firefox in Wayland mode for awhile now and never had problems until the new 90 update. Since the update, it crashes like crazy. I launch it, it crashes. I launch it, it actually stays up, I click on something like the menu and it crashes. I think I've sent Mozilla about 40 crash logs with their auto reporter thing.
I've also deleted my profile completely by removing ~/.mozilla and a fresh profile doesn't fix anything. I am using gnome with amdgpu + mesa if that matters.
I have since uninstalled 90 and downgraded back to 89. Anyone else having problems?
Offline
Yes, same here. Up to v 89 I had started Firefox with
MOZ_ENABLE_WAYLAND=1 firefox
and
export MOZ_DBUS_REMOTE=1
in ~/.bashrc.
After removing MOZ_ENABLE_WAYLAND=1, firefox 90 doesn't crash anymore - but it only uses xwayland. I haven't looked in bugzilla so far if there is a regression.
Offline
I read the new version has some changes in Web render. Maybe it's something related to that.
Offline
Yes, same here. Up to v 89 I had started Firefox with
MOZ_ENABLE_WAYLAND=1 firefox
and
export MOZ_DBUS_REMOTE=1
in ~/.bashrc.
After removing MOZ_ENABLE_WAYLAND=1, firefox 90 doesn't crash anymore - but it only uses xwayland. I haven't looked in bugzilla so far if there is a regression.
yeah i have MOZ_ENABLE_WAYLAND=1 in my ~/.config/environment.d/envvars.conf and its been working like a champ up until 90. i hope they fix it soon. until then i guess ill keep firefox blacklisted in pacman.conf and stay on 89.
maybe i'll use this as an excuse to give chromium a try with ozone.
Last edited by orlfman (2021-07-14 17:29:51)
Offline
You could try to search something about this error with journalctl, coredumpctl, start firefox from terminal and post here when you find something useful.
Offline
Found a solution here. Set gfx.webrender.compositor.force-enabled= false and all is well.
Offline
Found a solution here. Set gfx.webrender.compositor.force-enabled= false and all is well.
thank you i'll update and give that a try.
Offline
What is your environment like? What graphics drivers are you using?
I'm on amdgpu with a Vega10 iGPU with Wayland and hardware acceleration enabled, plus Webrender forced to enabled. I experience no crashes.
Offline
What is your environment like? What graphics drivers are you using?
I'm on amdgpu with a Vega10 iGPU with Wayland and hardware acceleration enabled, plus Webrender forced to enabled. I experience no crashes.
oh as i mentioned in my first post, i am using gnome, amdgpu, and mesa. on 89, according to about:support, its using WebRender. i'm going to try 90 again with forcing WebRender off.
edit:
setting gfx.webrender.compositor.force-enable to off as adventurer mentioned appears to be working for me too. no crashes yet.
Last edited by orlfman (2021-07-14 23:18:25)
Offline
Actually you're not forcing it off, but you don't force it to be on/enabled.
Since you stated you cleared your profile, I assume ff90 ships with a default setting that 'forces' webrender to be enabled, which seems a bit weird to me...
Do you confirm?
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
Actually you're not forcing it off, but you don't force it to be on/enabled.
Since you stated you cleared your profile, I assume ff90 ships with a default setting that 'forces' webrender to be enabled, which seems a bit weird to me...
Do you confirm?
yeah i did try making a new profile originally but after i downgraded back to 89, i made a new profile with 89 again. i had set gfx.webrender.compositor.force to false in 89 a few minutes before i upgraded to 90 again, and it stayed off after upgrading. i didn't want it crashing when trying to get to about:config in 90 to set it which is why i set it to false in 89 before hand.
reading this article from phoronix: https://www.phoronix.com/scan.php?page= … 0-Released makes it seem like its on by default now.
Offline
reading this article from phoronix: https://www.phoronix.com/scan.php?page= … 0-Released makes it seem like its on by default now.
There is a difference between "WebRender" and "WebRender Compositor". I guess there was no hardware compositor implemented for wayland in 89, some code was added in 90 that doesn't work well yet.
https://www.reddit.com/r/firefox/commen … n/ffdwnfv/
https://www.reddit.com/r/firefox/commen … n/ffc7a05/
https://bugzilla.mozilla.org/show_bug.cgi?id=1617498
The "webrender.compositor" setting enables offloading of some operations to the wayland compositor / hardware and not doing it in software in firefox itself. This has been enabled on windows for some time, and now the implememtation for wayland seems to be underway. It won't be added for X11, since that doesn't seem to improve things for the devs.
Last edited by progandy (2021-07-15 07:07:13)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
orlfman wrote:reading this article from phoronix: https://www.phoronix.com/scan.php?page= … 0-Released makes it seem like its on by default now.
There is a difference between "WebRender" and "WebRender Compositor". I guess there was no hardware compositor implemented for wayland in 89, some code was added in 90 that doesn't work well yet.
https://www.reddit.com/r/firefox/commen … n/ffdwnfv/
https://www.reddit.com/r/firefox/commen … n/ffc7a05/
https://bugzilla.mozilla.org/show_bug.cgi?id=1617498The "webrender.compositor" setting enables offloading of some operations to the wayland compositor / hardware and not doing it in software in firefox itself. This has been enabled on windows for some time, and now the implememtation for wayland seems to be underway. It won't be added for X11, since that doesn't seem to improve things for the devs.
yeah you're right. i found this bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1718688 they are aiming for 92 to be ready for daily use with gfx.webrender.compositor.force-enabled. they consider 90 to be very early, immature. i think i'll give firefox developer a try since its on 91 beta 2. that's post to have a lot more improvements with gfx.webrender.compositor.force-enabled
Offline
i found this bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1718688
According to this comment by Vlad Zahorodnii this is not a Firefox but a kwin bug which will be fixed in Plasma 5.22.4. Vlad should know - he's the kwin maintainer.
Offline
orlfman wrote:i found this bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1718688
According to this comment by Vlad Zahorodnii this is not a Firefox but a kwin bug which will be fixed in Plasma 5.22.4. Vlad should know - he's the kwin maintainer.
The crash was a firefox bug in 90. The 91 beta does not crash. There is a bug in kwin that freezes 91 beta. That freeze will be fixed with the next plasma release.
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
orlfman wrote:i found this bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1718688
According to this comment by Vlad Zahorodnii this is not a Firefox but a kwin bug which will be fixed in Plasma 5.22.4. Vlad should know - he's the kwin maintainer.
but these crashes happen on gnome too
Offline