Re: librewolf 153.0.4-1 segfault

På lørdag 15. august 2026 kl. 20:21, skrev Leah Rowe
<[email protected]>:

> 
> yaydn please can you look into this. you're the one who's been doing 
> updates recently.
> 
> i still don't have time to return yet, but i'll be back soon-ish. still 
> sorting out other stuff.
> 
> 
> Am 15.08.26 um 17:37 schrieb Ronald Dahlgren:
> > Hello ports,
> >
> > librewolf has been segfaulting after profile selection for about a
> > week now (maybe 10 days?). The behavior started after a `sysupgrade
> > -s` and has not been resolved with subsequent updates, so I thought
> > I'd report here. The first time I try to start it, the profile
> > selection screen appears. I choose a profile and a moment later it
> > segfaults. On subsequent runs, I can select the profile and the main
> > browser window will appear but all tabs have the "Gah. Your tab just
> > crashed." content. Even `about:blank` shows the same "gah" message.
> > `about:config` loads.
> >
> > If I select another profile, it will core dump the first time, and
> > then subsequently open the browser window with "Gah. Your tab just
> > crashed." messages.
> >
> > If I create a new profile, it will open the browser window with "Gah.
> > Your tab just crashed." messages. There is _some_ sort of interaction
> > with profiles here, but I can't tell if it's meaningful or not.
> >
> > It drops a core, but there isn't much helpful here:
> >
> > [rdahlgren@dark :: ~] $ librewolf --version
> > LibreWolf 153.0.4-1
> > [rdahlgren@dark :: ~] $ librewolf
> > ATTENTION: default value of option mesa_glthread overridden by environment.
> > librewolf[69235]: pledge "proc", syscall 195
> > librewolf[13877]: pledge "proc", syscall 195
> > ATTENTION: default value of option mesa_glthread overridden by environment.
> > librewolf[57614]: pledge "proc", syscall 195
> > librewolf[6793]: pledge "proc", syscall 195
> > [Parent 62539, IPC I/O Parent] WARNING: process 57614 exited on signal
> > 6: file librewolf-153.0.4-1/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:161
> > zsh: segmentation fault (core dumped)  librewolf
> > [rdahlgren@dark :: ~] $ gdb -c librewolf.core
> > GNU gdb 6.3
> > Copyright 2004 Free Software Foundation, Inc.
> > GDB is free software, covered by the GNU General Public License, and you are
> > welcome to change it and/or distribute copies of it under certain conditions.
> > Type "show copying" to see the conditions.
> > There is absolutely no warranty for GDB.  Type "show warranty" for details.
> > This GDB was configured as "amd64-unknown-openbsd8.0".
> > Core was generated by `librewolf'.
> > Program terminated with signal 11, Segmentation fault.
> > #0  0x00000b00d7bc69db in ?? ()
> > (gdb) bt
> > #0  0x00000b00d7bc69db in ?? ()
> > #1  0x69660874780668f0 in ?? ()
> > #2  0x00000b00f704c3fb in ?? ()
> > #3  0x00000000000000d8 in ?? ()
> > #4  0x0000040000000a40 in ?? ()
> > #5  0x0000000000000000 in ?? ()
> >
> >
> > I was using librewolf happily without issue prior. Happy to provide
> > details or snippets from relevant config files on request.
> >
> > Thank you,
> > Ron
> >

Been trying to replicate this, but all I have access to is intel x86_64.

Does this also happen in www/mozilla-firefox for you?

I updated librewolf, so hopefully that might do it.

If not there were a lot of AMD/drm driver churn this month
particularly August 3rd, 6th, 7th, and 10th. Ideally use snapshots
between these dates to triangulate the possible problem. Though that
might be hard to find in the mirrors.

I read some driver changes got reverted upstream in 7.1.x and 6.18.x,
so maybe the next drm changes in cvs will possibly fix this if it is not
application specific.

If it is librewolf, but not firefox having this issue. I am not sure
what was changed in the source compared to one another.

Sorry I don't have much news on this.

Hope that helps. May you have a cool one and stay hydrated.
--
yaydn