Summary: | www-client/firefox-117: Isolated Web Co[17972]: segfault at 88 ip 00007fcb9306d012 sp 000 07fffac4c8528 error 4 in libxul.so[7fcb91234000+3cf5000] | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | awilum <r.ziman8> |
Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | confabulate |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build log.
emerge --info distcc hosts emerge --info www-client/firefox |
Description
awilum
2023-09-12 12:46:44 UTC
Created attachment 870349 [details]
Build log.
Stopped after configuration done.
So does it not happen with ublock origin disabled? You should also try the latest versions (of firefox, +ubo). Nothing obvious stands out, but I would try to compile it without distcc and strip any weird *FLAGS off too. Hi, Joonas Niilola, > So does it not happen with ublock origin disabled? Yes, it doesn't happen with origin disabled. > You should also try the latest versions (of firefox, +ubo). I have tested with firefox-117.0.1 & uBO 1.52.0. FEATURES: without distcc When firefox-117.0.1 is compiled with clang & lto, also with clang & -lto, no problem. But with -clang & -lto, maybe also with -clang & lto (I didn't tested this one), I have had this, in dmesg logs: [ 4951.498984] Isolated Web Co[7861]: segfault at 88 ip 00007f8e7e519dca sp 00007ffe2138aa28 error 4 in libxul.so[7f8e7c6e1000+3cf5000] likely on CPU 18 (core 2, socket 0) [ 4951.499003] Code: f0 48 29 f8 74 23 49 0f af f8 49 0f af c0 49 0f af f0 49 0f af c8 48 8d 7c 3a 08 48 89 c2 48 01 fe 48 01 cf e9 df 20 1d fe c3 <48> 8b 07 8b 08 48 8d 50 08 48 8d 4c c8 08 48 89 d0 48 39 c1 74 1f So, to avoid this problem, we need to compile with clang ? Best regards. Hmm, could you provide "emerge --info"? I wonder if some library is broken with your *FLAGS setting, or distcc (are you using pump?). Wouldn't be the first time libs aren't breaking when building them, but show some random runtime issues with their rdeps. Especially when related to multimedia. Could also be related to alsa<->pulseaudio, since upstream binary is always built with pulseaudio support enabled. We just get around with using apulse, but with source-version, you can disable pulseaudio. It's really hard to day. You may have to backtrace the issue to find the exact problem. It's better than guessing. https://wiki.gentoo.org/wiki/Debugging Created attachment 870930 [details]
emerge --info
Created attachment 870931 [details]
distcc hosts
There is only localhost
> I wonder if some library is broken with your > *FLAGS setting, or distcc (are you using pump?). I did not use pump mode. Also I have only localhost in my hosts for distcc. > Could also be related to alsa<->pulseaudio, > since upstream binary is always built with pulseaudio support enabled. > We just get around with using apulse, but with source-version, you can disable pulseaudio. Pulseaudio is not installed, I have only both alsa & pipewire (with wireplumber). > It's really hard to day. You may have to backtrace the issue to find the exact problem. > It's better than guessing. > >https://wiki.gentoo.org/wiki/Debugging I will take a look at it. Created attachment 887913 [details]
emerge --info www-client/firefox
This problem is not related to distcc - I don't use distcc and have the same segfault here running firefox on Wayland with two monitors. It's been happening for different versions of firefox. It crashes the whole OS and necessitates a hard reboot. It is always repeatable by:
1. Placing PC in sleep and waking it up.
2. Launching firefox and start browsing.
Some random time after firefox is launched (usually between 15 to 50 minutes) the application segfaults irrecoverably. A typical message shown in the log:
kernel: Isolated Web Co[24562]: segfault at 2100 ip 00007f7d18c5aad0 sp 00007ffde8c97e50 error 4 in libxul.so[7f7d18c1a000+5773000] likely on CPU 3 (core 3, socket 0)
I have placed the Firefox cache on /tmp, but it makes no difference. I have also enabled in about:config with no success:
gfx.webrender.all
gfx.webrender.compositor
(this was suggested in some old Fedora bug report of Firefox-60).
From a fresh reboot Firefox could be used continuously and for many days and hours (5-10hr) at a time with no problem manifesting, but if if launched and used after the PC is put on sleep and woken up it will always crash. I attach emerge --info.
|