On Sunday 28 May 2017 18:09:19 O. Hartmann wrote:
> Am Sun, 28 May 2017 08:54:35 -0700
> Pete Wright <p...@nomadlogic.org> 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
> 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
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"