[Wayland] Crash in [@ libc-2.31.so@0xfc29d | radeonsi_dri.so@0x845d5a] (Fission or WebRender on Linux?)
Categories
(Core :: Graphics: WebRender, defect, P2)
Tracking
()
Fission Milestone | M6 |
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox73 | --- | unaffected |
firefox74 | --- | unaffected |
firefox75 | --- | disabled |
firefox76 | --- | disabled |
People
(Reporter: bobsfree, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
32.77 KB,
application/json
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
Navigated to various websites including Reddit.
Actual results:
The content process crashed with the above signature.
Expected results:
Browsing the webpage proceeded normally.
Comment 2•4 years ago
|
||
Hi John,
Can you add any additional step to reproduce this crash? For how long did you navigated within the browser? How many tabs were open?
I can see on the attached file there are 14 crashes included. I will move this to the right component so that the developers can take a look at the crash reports.
Please test if the issue occurs to you in safe mode (add-ons disabled). Here is a link that can help you do that:
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
If the issue persists, also test it using a fresh profile, you can find the steps to do that below:
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager
Best,
Clara.
Hi Clara,
In terms on when I get these crashes, I can reliably reproduce this on new reddit, and on the login page for ebay (regardless of the region). It doesn't seem to matter how long I browse, or how many tabs are open. On average, I say I would have between 5 - 20 tabs open at any time.
The issue persists with all addons disabled, and I can reproduce in a new profile. In fact, I have refreshed several times when I ran into this issue, which I thought may assist.
I can also reproduce with fission disabled. I can also reproduce this with dmabuf VAAPI disabled.
It is worth noting that I am running webrender on Wayland. Perhaps this related? I cannot reproduce in safe mode.
I am running a Radeon 5500XT on mesa 20.0.1 on Fedora Branched (i.e. Fedora 32 pre-release). I am not having issues with programs other than Firefox.
Just thought I'd mention, I am more than happy to profile this issue, or try any other steps that may assist. I just need to be pointed in the right direction. Thanks for the help.
Comment 5•4 years ago
|
||
This bug is a graphics crash, not a performance bug.
This is top crash #6 among Fission Nightly users on Linux. The crashes appear to be a regression starting in 75 Nightly. 99 out of 103 crash reports have Fission enabled, so this crash is mostly Fission but exclusively. Perhaps this is a WebRender race condition and Fission alters the timing to make the crash more likely?
This bug is for crash report bp-0c3a32ae-6ea5-47aa-9726-0a3790200312.
Top 10 frames of crashing thread:
0 libc-2.31.so libc-2.31.so@0xfc29d
1 radeonsi_dri.so radeonsi_dri.so@0x845d5a
2 radeonsi_dri.so radeonsi_dri.so@0x2f8681
3 radeonsi_dri.so radeonsi_dri.so@0x27e0ef
4 radeonsi_dri.so radeonsi_dri.so@0xcfcf91
5 radeonsi_dri.so radeonsi_dri.so@0xcfcf91
6 radeonsi_dri.so radeonsi_dri.so@0x27f171
7 radeonsi_dri.so radeonsi_dri.so@0xfee8a
8 radeonsi_dri.so radeonsi_dri.so@0x15c4fb
9 radeonsi_dri.so radeonsi_dri.so@0x10290d
Comment 6•4 years ago
|
||
Andrew, you're a Linux contact person and in Toronto where we might have hardware.
This is a topcrash with webrender and fission, so I'm calling it a P2.
Updated•4 years ago
|
Updated•4 years ago
|
Comment 7•4 years ago
|
||
All crashes have "gpuProcess":{"status":"blocked"} in telemetry environment.
Comment 8•4 years ago
|
||
It seems all crashes are from John.
100 of 103 crashes from the last 3 months have the same graphics adapter (0x7340) and the "Bitwarden" password manager extension installed.
101 have en-AU locale and contain "knurd" in telemetry environment.
(One of the few VAAPI crashes: bp-6afe0d0d-6150-41a6-924e-4f0f10200312)
Just some further info. The "knurd" referred to above, are the vanilla mainline kernel releases offered by Fedora as at:
https://fedoraproject.org/wiki/Kernel_Vanilla_Repositories
They are not the patched "Fedora" kernel releases that eventually do land in stable, but should be the same as will be used in any distribution that relies on a vanilla kernel when it does release.
Happy to try reverting to a patched kernel if that would assist.
Reporter | ||
Comment 10•4 years ago
|
||
I can confirm that I can also reliably reproduce this on the stock Fedora 32 kernel. It seems likely that I am the only one hitting this at this stage, due to not many users yet using Fedora 32 beta. The numbers on this one may increase once Fedora 32 becomes more widely adopted.
Reporter | ||
Comment 11•4 years ago
|
||
Sorry for the bugspam.
I just thought I would include the exact URLs that seem to 100% reproducible on my end.
Logged in to Reddit, the URL https://www.reddit.com/message/inbox, crashes immediately with 100% reliability.
I can also immediately with 100% reliability reproduce a crash on browsing to https://signin.ebay.com.au/ws/eBayISAPI.dll?SignIn&ru=https%3A%2F%2Fwww.ebay.com.au%2F.
Comment 12•4 years ago
|
||
(In reply to Chris Peterson [:cpeterson] from comment #5)
This bug is for crash report bp-0c3a32ae-6ea5-47aa-9726-0a3790200312.
(In reply to Jan Andre Ikenmeyer [:darkspirit] from comment #8)
(One of the few VAAPI crashes: bp-6afe0d0d-6150-41a6-924e-4f0f10200312)
These crashes also have "Crash Address: 0x138".
Description
•