From owner-freebsd-current@freebsd.org Tue May 30 18:01:02 2017 Return-Path: Delivered-To: freebsd-current@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 7A61BB957D5 for ; Tue, 30 May 2017 18:01:02 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (unknown [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 638847313D for ; Tue, 30 May 2017 18:01:02 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.26] (cpe-23-242-94-236.socal.res.rr.com [23.242.94.236]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 146e579a TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Tue, 30 May 2017 11:01:00 -0700 (PDT) Subject: Re: INO64 Effecting Firefox To: freebsd-current@freebsd.org References: From: Pete Wright Message-ID: Date: Tue, 30 May 2017 11:00:59 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 18:01:02 -0000 On 05/28/2017 08:54, Pete Wright wrote: > Hi all, > > I can't imagine that this is related to INO64, but since upgrading my > world and kernel on drm-next (which merged upstream CURRENT as of May > 27 which should include the ino64 work) I am having segfaults running > firefox. Previous to this firefox was very stable for work/personal > daily use. > > The error I'm seeing is: > Full message: TypeError: malformed UTF-8 character sequence at offset 0 > > Firefox does start and I can load a page or two before it sefaults. > > The full console output is here: > > https://gist.github.com/anonymous/555202b1452503ad9e26750168f87d5f > > > Posting this here in the off chance that it's either related to ino64, > or some other recent change has caused this problem. > Just to close the loop on this. It looks like after upgrading to the latest official packages available i can now run Firefox w/o crashing. I am still getting the UTF-8 error mentioned above, but have not segfaulted yet. So apparently that error was a red herring. Interesting enough, firefox was *not* on the packages that was upgraded - so i assume a shared library was updated that trigger the fault. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA