Random crashes on Wayland with NVIDIA 555.58.02
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
People
(Reporter: rockyamethyst2, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0
Steps to reproduce:
Use the RPM provided by the Fedora 40 repos (128.0-1.fc40, build ID 20240709131756)
Set MOZ_ENABLE_WAYLAND to 1
Use it for a while, sometimes it can take minutes, sometimes it's less. Which websites are opened does not seem to matter.
Actual results:
Firefox crashes, and sometimes, tabs can crash without taking Firefox down entirely.
Terminal log and the about:support report (from an xwayland run of firefox) is in the attached zip file.
Expected results:
Firefox shouldn't have crashed.
|
||
Updated•1 year ago
|
|
||
Comment 1•1 year ago
|
||
Please loot at about:crashes , submit them and attach the crash ID here.
Thanks.
|
|
||
Updated•1 year ago
|
|
|
||
Comment 2•1 year ago
|
||
May be dupe of Bug 1907511.
|
Reporter | |
Comment 3•1 year ago
|
||
(In reply to Martin Stránský [:stransky] (ni? me) from comment #1)
Please loot at about:crashes , submit them and attach the crash ID here.
Thanks.
bp-d4a893e1-1345-480d-9de6-efffc0240712, 12/07/2024, 07:25 (GMT-3)
|
|
||
Comment 4•1 year ago
|
||
Interesting, looks like NS_ABORT_OOM(unsigned long) which is out of memory. Can you attach more crash ID's?
Also can you please try Mozilla binary directly?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_Mozilla_binaries
Thanks.
|
|
Reporter | |
Comment 5•1 year ago
|
||
bp-2d3fa737-80cd-4703-8316-6ccb60240712
bp-d4a893e1-1345-480d-9de6-efffc0240712
bp-216a92f0-7fc6-4079-bb89-45d880240712
Original binary crash ID's above, ran as asked (with wayland) from wiki. (MOZ_ENABLE_WAYLAND=1 ./firefox -ProfileManager -no-remote)
RPM Binary crashes way less often, guess it's because of my about:config settings? (Since it's set up to have hardware decoding for h264 and VP9 videos, via the nvidia-vaapi-driver project), i can reset them if it is needed, since the time between #4 and now, I've only had 2 tab crashes and a single "full" crash.
|
|
||
Comment 6•1 year ago
|
||
(In reply to rockyamethyst2 from comment #5)
RPM Binary crashes way less often, guess it's because of my about:config settings? (Since it's set up to have hardware decoding for h264 and VP9 videos, via the nvidia-vaapi-driver project), i can reset them if it is needed, since the time between #4 and now, I've only had 2 tab crashes and a single "full" crash.
Not sure. It's OOM crash (system is out of memory) and it means a system component like OOM killer terminated Firefox due to low system memory state.
|
|
Reporter | |
Comment 7•1 year ago
|
||
That's weird, Firefox never crashed on me before due to going OOM (and that's with opening a zillion tabs while looking some stuff up, constantly switching to read around), and the crash is gone entirely when I disable Wayland and use xWayland, i assume it'd be fixed too if i used x11 to test it. (Which i should test, actually, i'll switch later and see how that goes).
Will also run the Mozilla binary for a while on x11 to see if the same symptom arises, I don't have many ideas after that though.
|
|
Reporter | |
Comment 8•1 year ago
|
||
No crashes on X11 so far, saw that bug 1907511 got fixed, so went to test nightly, on wayland again.
bp-938be812-4fb2-4a9b-a9be-0f31c0240713 - Latest build, crashed seconds after boot (and i'm pretty sure the fix for the other bug is included in here), can't be my system OOM'ing it, right? (since i kept track of ram usage, it never got to use all i have, which is 8gb, system usage sat at 5-6gb) or does Firefox have it's own OOM for misbehaving tabs? Doesn't make sense (to me at least) why it would crash entirely, going as far to bring the crash reporter up.
I'm also experiencing this bug on my install of F40 with NVIDIA 555 driver installed.
OS error reporter reports that firefox-bin was killed by SIGSEGV.
I've tried both the stable and beta version from flathub and I've cleared user data between both installs.
Using flatseal to force FF through Xwayland by turning off access to wayland socket seems to resolve the issue.
|
|
||
Comment 10•1 year ago
|
||
(In reply to rockyamethyst2 from comment #8)
No crashes on X11 so far, saw that bug 1907511 got fixed, so went to test nightly, on wayland again.
bp-938be812-4fb2-4a9b-a9be-0f31c0240713 - Latest build, crashed seconds after boot (and i'm pretty sure the fix for the other bug is included in here), can't be my system OOM'ing it, right? (since i kept track of ram usage, it never got to use all i have, which is 8gb, system usage sat at 5-6gb) or does Firefox have it's own OOM for misbehaving tabs? Doesn't make sense (to me at least) why it would crash entirely, going as far to bring the crash reporter up.
It's null pointer crash at libnss_resolve.so.2 which is not related to graphics / NVIDIA at all. It's a crash at _nss_resolve_gethostbyname4_r() which comes from system library. I'd try Mozilla provided binaries first as this may be a bug in system NSS library (Fedora one in this case).
|
|
Reporter | |
Comment 11•1 year ago
|
||
Nightly wasn't installed as a system package (via DNF), I downloaded it directly from the website and ran from there, there doesn't seem to be any (official at least) ways to install it as a package in Fedora (no Flatpak either). What would "Mozilla provided binary" mean then, I did what the wiki you sent reccomended.
|
|
||
Comment 12•1 year ago
|
||
(In reply to rockyamethyst2 from comment #11)
Nightly wasn't installed as a system package (via DNF), I downloaded it directly from the website and ran from there, there doesn't seem to be any (official at least) ways to install it as a package in Fedora (no Flatpak either). What would "Mozilla provided binary" mean then, I did what the wiki you sent reccomended.
Yes, you did that well then, it's exactly that. Yeah I didn't notice the crash https://crash-stats.mozilla.org/report/index/938be812-4fb2-4a9b-a9be-0f31c0240713 comes from Nightly and not from Fedora rpm.
It means you're seeing NSS crashes in Mozilla binary. Please file a new bug for it for NSS component and attach the crash ID there.
Thanks.
Description
•