Date: Thu, 25 Jan 2018 14:42:05 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 225364] devel/nspr security/nss: latest upgrade makes firefox-esr and thunderbird dump core Message-ID: <bug-225364-21738-LByyUK0bjQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-225364-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-225364-21738@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225364 Brad Sliger <code@sliger.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |code@sliger.org --- Comment #2 from Brad Sliger <code@sliger.org> --- I think this is happening to me. Setting NSS_DEFAULT_DB_TYPE=3Ddbm in Fire= fox's environment keeps Firefox from crashing. Thanks! Firefox will start up, do its initial splashes and animations for a few seconds, then crash with messages like the following: [Child 81768] ###!!! ABORT: Aborting on channel error.: file /usr/ports/www/firefox-esr/work/firefox-52.6.0esr/ipc/glue/MessageChannel.c= pp, line 2152 [Child 81768] ###!!! ABORT: Aborting on channel error.: file /usr/ports/www/firefox-esr/work/firefox-52.6.0esr/ipc/glue/MessageChannel.c= pp, line 2152 zsh: bus error firefox dmesg will show something like: pid 77538 (firefox), uid 1009: exited on signal 10 pid 81768 (firefox), uid 1009: exited on signal 11 Firefox won't crash for me if it already has its configuration files. If i= t's started in an empty sandbox, without setting NSS_DEFAULT_DB_TYPE=3Ddbm, it'= ll crash fairly quickly. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-225364-21738-LByyUK0bjQ>