From owner-freebsd-questions@freebsd.org Wed Aug 12 01:21:52 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 890DF99E218 for ; Wed, 12 Aug 2015 01:21:52 +0000 (UTC) (envelope-from nomadlogic@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 677001987 for ; Wed, 12 Aug 2015 01:21:52 +0000 (UTC) (envelope-from nomadlogic@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6681F99E216; Wed, 12 Aug 2015 01:21:52 +0000 (UTC) Delivered-To: questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 650C899E215 for ; Wed, 12 Aug 2015 01:21:52 +0000 (UTC) (envelope-from nomadlogic@gmail.com) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DC7071986 for ; Wed, 12 Aug 2015 01:21:51 +0000 (UTC) (envelope-from nomadlogic@gmail.com) Received: by lalv9 with SMTP id v9so1273897lal.0 for ; Tue, 11 Aug 2015 18:21:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pMMUufzn6WCeET4BsJalrfF7jCgdw0C1OHluaNdtyUo=; b=ckuWhK5tyOhTp/MJEwsIMcLra0bJwxw86XO/FpWYoThf4EJn0MkEKNO3M1E1hwm1pR vyH7JVo1m8OFlXadiq0FYRn4Rke9S1/rX9fTv5ULJBGTFhRE4ri9tuVxIQUKpeAvz9dX pDXS3XNopgUOrGRFyrddKTazqBbN+4D4cz79qHcPbdiWkFpz/xiwUDUtya2hX4d3Ru4o ThMdLy6BbVszxKmIl1zgPcRLC5bKMhZxUqdf0lehq8CsyfOQx12NB+x0cr1BDxdwhYd0 meLIWeUsPxgMN1Mb/UvbJG5xCIvtLPK8HvncCYPRTGJ8G8Vz7jbfDs3G3v8/0HwjRVD6 hVvQ== MIME-Version: 1.0 X-Received: by 10.112.161.40 with SMTP id xp8mr29435292lbb.71.1439342509816; Tue, 11 Aug 2015 18:21:49 -0700 (PDT) Received: by 10.25.16.218 with HTTP; Tue, 11 Aug 2015 18:21:49 -0700 (PDT) Received: by 10.25.16.218 with HTTP; Tue, 11 Aug 2015 18:21:49 -0700 (PDT) In-Reply-To: <20150812002205.GB82089@slackbox.erewhon.home> References: <20150812002205.GB82089@slackbox.erewhon.home> Date: Tue, 11 Aug 2015 18:21:49 -0700 Message-ID: Subject: Re: firefox core-dump on 10.1-RELEASE? From: pete wright To: Roland Smith Cc: freebsd-questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Aug 2015 01:21:52 -0000 On Aug 11, 2015 5:22 PM, "Roland Smith" 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. Cheers, -pete