FS#69457 - [firefox 85.0] display crash at launch
Attached to Project:
Arch Linux
Opened by Alexandre ZANNI (noraj) - Thursday, 28 January 2021, 09:58 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 21 April 2021, 10:17 GMT
Opened by Alexandre ZANNI (noraj) - Thursday, 28 January 2021, 09:58 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 21 April 2021, 10:17 GMT
|
Details
Description:
- Launching firefox in normal mode create a visual glitch where the firefox windows displays the content of the window behind instead of the actual content, and when you want to right click on the task manager and close firefox it will tell the firefox process is not responding - launching in safe mode works - it's tempting to think it's due to a plugin or a bad settings, but launching in normal mode with all plugin disables doesn't work and I changed nothing in about:config only ultra classic stuff like the download folder - sometimes after killing the process or by launching in safe mode firefox suggest to make a "refresh" that will keep your data and plugins but will reset firefox settings, after the refresh firefox works for the current boot, you can close and relaunch the process, but at next boot it will start to crash again so I need to make a firefox "refresh" at each boot - it started to happen with the 85.0 the 2021-01-26 so I hope it's due to the new version - it happens wathever the kernel is (vanilla, zen, lts) Additional info: * package version(s) 85.0 Operating System: Arch Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.4.92-1-lts OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Steps to reproduce: - just launch firefox (but maybe due to a specific environment so it may not be reproducible for everyone) |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Wednesday, 21 April 2021, 10:17 GMT
Reason for closing: Fixed
Additional comments about closing:
85.0.2 solves the issue as noted in the upstream bug entry.
Wednesday, 21 April 2021, 10:17 GMT
Reason for closing: Fixed
Additional comments about closing:
85.0.2 solves the issue as noted in the upstream bug entry.
Which is weird because FF 85 release note says.
> Changes for add-on developers
>
> No changes.
Cf. https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/85
So what changed between FF 84 & 85 that broke the browser? I'll request a closure since it's possibly due to the plugin.
Using safe mode doesn't solve the problem for me. And i don't have firefox-extension-arch-search.
Trying without or with webrender same problem.
If i kill the window and relaunch, sometimes, like 1/40 ~ it work... very weird.
Seems to be an issue running on both XWayland and Wayland (AMDGPU, RX 5500XT).
I see multiple hang/freeze/crash bugs submitted upstream under the Untriaged category, which may be related. If anyone has access to a problem machine please chime in or submit a bug there -- unfortunately I can't be online to actively track this until next week.
If it is an upstream issue there is also Mozregression [3] to locate the regression range.
[1] https://aur.archlinux.org/packages/firefox-bin/
[2] https://aur.archlinux.org/packages/firefox-nightly/
[3] https://wiki.mozilla.org/Auto-tools/Projects/Mozregression
firefox-nightly is working fine also
Not sure whether those imply an upstream or packaging issue however
Firefox version 85.0-1
Operating System: Arch Linux
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.11-arch1-1
OS Type: 64-bit
Processors: 12 × AMD Ryzen 5 2600 Six-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: GeForce RTX 2060/PCIe/SSE2
EDIT: Doing firefox -P and creating a completely new profile (rather than switching to another existing one) seems to be a lasting (touch wood) workaround.
No, it isn't related to layers.acceleration.force-enabled for me.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1679933
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1689032