From owner-freebsd-current@freebsd.org Sun May 28 16:45:03 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 56BB4D85871 for ; Sun, 28 May 2017 16:45:03 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from oleg.opentransfer.com (oleg.opentransfer.com [91.217.144.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "oleg-10.opentransfer.com", Issuer "oleg-10.opentransfer.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B85161E28 for ; Sun, 28 May 2017 16:45:02 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from asus.theweb.org.ua ([10.0.8.4]) by oleg.opentransfer.com (8.15.2/8.15.2) with ESMTPS id v4SGpQHC098967 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Sun, 28 May 2017 19:51:29 +0300 (EEST) (envelope-from oleg@theweb.org.ua) Received: from asus.theweb.org.ua (localhost [127.0.0.1]) by asus.theweb.org.ua (8.15.2/8.15.2) with ESMTPS id v4SGii1h077112 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sun, 28 May 2017 19:44:44 +0300 (EEST) (envelope-from oleg@theweb.org.ua) Received: (from oleg@localhost) by asus.theweb.org.ua (8.15.2/8.15.2/Submit) id v4SGiiMr077111 for freebsd-current@freebsd.org; Sun, 28 May 2017 19:44:44 +0300 (EEST) (envelope-from oleg@theweb.org.ua) X-Authentication-Warning: asus.theweb.org.ua: oleg set sender to oleg@theweb.org.ua using -f From: "Oleg V. Nauman" To: freebsd-current@freebsd.org Subject: Re: INO64 Effecting Firefox Date: Sun, 28 May 2017 19:44:43 +0300 Message-ID: <5493690.zc92PMVLEF@asus.theweb.org.ua> Organization: Private person User-Agent: KMail/4.14.10 (FreeBSD/12.0-CURRENT; KDE/4.14.30; amd64; ; ) In-Reply-To: <20170528180919.7821e484@thor.intern.walstatt.dynvpn.de> References: <20170528180919.7821e484@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Mailman-Approved-At: Sun, 28 May 2017 17:15:50 +0000 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: Sun, 28 May 2017 16:45:03 -0000 On Sunday 28 May 2017 18:09:19 O. Hartmann wrote: > Am Sun, 28 May 2017 08:54:35 -0700 > > Pete Wright schrieb: > > 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. > > > > Cheers! > > > > -pete > > I see similar problems. Out of the blue, firefox crashes. > But in my case, firefox is "old", since it doesn't compile with > WITH_LLD_IS_LD due to a very strange error (Bug 218808). > > The binary I run und CURRENT (FreeBSD 12.0-CURRENT #8 r319001: Sun May 28 > 00:21:16 CEST 2017 amd64, WITH_LLD_IS_LD=yes) if as of > > firefox-53.0_2,1 > Name : firefox > Version : 53.0_2,1 > Installed on : Sun Apr 16 10:17:14 2017 CEST > Origin : www/firefox > Architecture : FreeBSD:12:amd64 > > I got a kind of relief (means: the frequence of crashes is reduced) when > starting to rebuild all ports again (I'm staying with make and portmaster) > to meet ABI requirements after ino64 has been introduced. > > Another strange behaviour is: firefox crashes very likely very often when > started. Once it has run a while, I can consider it "stable". It doen not > crash then. Please try to rebuild firefox. It helps me today with firefox-esr segfaulting on my desktop running 12.0-CURRENT r318856 From my limited understanding of stacktraces it was related to libthr changes.