Date: Wed, 12 Aug 2015 14:12:42 +0100 From: Arthur Chance <freebsd@qeng-ho.org> Cc: freebsd-questions <questions@freebsd.org> Subject: Re: firefox core-dump on 10.1-RELEASE? Message-ID: <55CB464A.8070707@qeng-ho.org> In-Reply-To: <CAGBmCT7r%2Bs0c4%2BK1fw5Lh-VmPPCJtEv0SMM=agb3VaXvUYmhtg@mail.gmail.com> References: <CAGBmCT4oP0pwP%2B7A-CAeRs18t7yJcy-oXOBkkjijc4DUryAOag@mail.gmail.com> <20150812002205.GB82089@slackbox.erewhon.home> <CAGBmCT7r%2Bs0c4%2BK1fw5Lh-VmPPCJtEv0SMM=agb3VaXvUYmhtg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/08/2015 02:21, pete wright wrote: > On Aug 11, 2015 5:22 PM, "Roland Smith" <rsmith@xs4all.nl> wrote: >> >> On Tue, Aug 11, 2015 at 12:08:26PM -0700, pete wright wrote: >>> Hi, >>> I recently upgraded firefox on my 10.1-RELEASE workstation via pkg and >>> now have periodic core dumps. I was wondering if anyone else has >>> observed this behaviour? If not I will attempt to get a debug build >>> created locally and try to reproduce the fault. Here's my info: >> >> Yep, more people have noticed it. >> >>>> uname -ar && pkg info |grep firefox >>> FreeBSD pop.rubicorp.com 10.1-RELEASE-p10 FreeBSD 10.1-RELEASE-p10 #0: >>> Wed May 13 06:54:13 UTC 2015 >>> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >>> >>> firefox-40.0,1 Web browser based on the browser portion of Mozilla >> >> A temporary fix is implemented in 40.0_1,1; it works pretty well; have > only >> had one crash since. >> >> But today the port was updated to 40.0_2,1, and 40.0_3,1 which failed to > link >> for me. It seems that firefox is once again churning a little bit, as it >> sometimes does. >> >> Since firefox is quite a big build, I tend to make a package of the > installed >> version before upgrading, so I can always go back if it works. >> > Thanks Roland for the reply. > > Fwiw to close this thread out - here is the fix mentioned in the previous > twitter > > "use about:config and set > layers.offmainthreadcomposition.enabled > to false." > > This has done the trick for me so far. Just had a crash with that change done. However, FF lasted about 6 hours, whereas it was lasting less than an hour before. -- Those who do not learn from computing history are doomed to GOTO 1
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55CB464A.8070707>