Date: Mon, 29 May 2017 06:41:03 +0000 From: =?iso-8859-1?Q?M=26S_-_Krasznai_Andr=E1s?= <Krasznai.Andras@mands.hu> To: "Oleg V. Nauman" <oleg@theweb.org.ua>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: RE: INO64 Effecting Firefox Message-ID: <c5ec7340a0a44a438cfa21cfe7fdb226@MSEXCH13.mands.hu> In-Reply-To: <5493690.zc92PMVLEF@asus.theweb.org.ua> References: <d1ad98a8-e542-adf8-eb7f-14f423e7d0fc@nomadlogic.org> <20170528180919.7821e484@thor.intern.walstatt.dynvpn.de> <5493690.zc92PMVLEF@asus.theweb.org.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Since last Thursday's update of Freebsd-12-current kernel, world (and preco= mpiled packeges with pkg update/upgrade) I experience rather large number o= f Firefox crashes. Sometimes it crashes without opening any pages (I just s= tarted and left firefox for a few minutes, it crashes with the same error:= =20 A coding exception was thrown and uncaught in a Task. Full message: TypeError: malformed UTF-8 charachter sequence at offset 0 etc. )=20 Version numbers: FreeBSD-12-0-CURRENT #318917; firefox-53.0.3,1 best regards Andr=E1s Krasznai -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freeb= sd.org] On Behalf Of Oleg V. Nauman Sent: Sunday, May 28, 2017 6:45 PM To: freebsd-current@freebsd.org Subject: Re: INO64 Effecting Firefox On Sunday 28 May 2017 18:09:19 O. Hartmann wrote: > Am Sun, 28 May 2017 08:54:35 -0700 >=20 > Pete Wright <pete@nomadlogic.org> schrieb: > > Hi all, > >=20 > > I can't imagine that this is related to INO64, but since upgrading=20 > > my world and kernel on drm-next (which merged upstream CURRENT as of=20 > > May 27 which should include the ino64 work) I am having segfaults=20 > > running firefox. Previous to this firefox was very stable for=20 > > work/personal daily use. > >=20 > > The error I'm seeing is: > > Full message: TypeError: malformed UTF-8 character sequence at=20 > > offset 0 > >=20 > > Firefox does start and I can load a page or two before it sefaults. > >=20 > > The full console output is here: > >=20 > > https://gist.github.com/anonymous/555202b1452503ad9e26750168f87d5f > >=20 > >=20 > > Posting this here in the off chance that it's either related to=20 > > ino64, or some other recent change has caused this problem. > >=20 > > Cheers! > >=20 > > -pete >=20 > I see similar problems. Out of the blue, firefox crashes. > But in my case, firefox is "old", since it doesn't compile with=20 > WITH_LLD_IS_LD due to a very strange error (Bug 218808). >=20 > The binary I run und CURRENT (FreeBSD 12.0-CURRENT #8 r319001: Sun May=20 > 28 > 00:21:16 CEST 2017 amd64, WITH_LLD_IS_LD=3Dyes) if as of >=20 > 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 >=20 > I got a kind of relief (means: the frequence of crashes is reduced)=20 > when starting to rebuild all ports again (I'm staying with make and=20 > portmaster) to meet ABI requirements after ino64 has been introduced. >=20 > Another strange behaviour is: firefox crashes very likely very often=20 > when started. Once it has run a while, I can consider it "stable". It=20 > doen not crash then. Please try to rebuild firefox. It helps me today with firefox-esr segfault= ing on my desktop running 12.0-CURRENT r318856 From my limited understandi= ng of stacktraces it was related to libthr changes. _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/= listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c5ec7340a0a44a438cfa21cfe7fdb226>