Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 May 2017 18:09:19 +0200
From:      "O. Hartmann" <ohartmann@walstatt.org>
To:        Pete Wright <pete@nomadlogic.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: INO64 Effecting Firefox
Message-ID:  <20170528180919.7821e484@thor.intern.walstatt.dynvpn.de>
In-Reply-To: <d1ad98a8-e542-adf8-eb7f-14f423e7d0fc@nomadlogic.org>
References:  <d1ad98a8-e542-adf8-eb7f-14f423e7d0fc@nomadlogic.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/u=TtxToWBmbcUfvfDUO5Iii
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Am Sun, 28 May 2017 08:54:35 -0700
Pete Wright <pete@nomadlogic.org> schrieb:

> Hi all,
>=20
> I can't imagine that this is related to INO64, but since upgrading my=20
> world and kernel on drm-next (which merged upstream CURRENT as of May 27=
=20
> which should include the ino64 work) I am having segfaults running=20
> firefox.  Previous to this firefox was very stable for work/personal=20
> daily use.
>=20
> The error I'm seeing is:
> Full message: TypeError: malformed UTF-8 character sequence at 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 ino64,=20
> or some other recent change has caused this problem.
>=20
> Cheers!
>=20
> -pete
>=20
>=20

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 0=
0:21:16 CEST
2017 amd64, WITH_LLD_IS_LD=3Dyes) 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 st=
arting 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 s=
tarted. Once
it has run a while, I can consider it "stable". It doen not crash then.=20

--=20
O. Hartmann

Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr
Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.=
 4 BDSG).

--Sig_/u=TtxToWBmbcUfvfDUO5Iii
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWSr2LwAKCRDS528fyFhY
lPDCAgCGWbOHEg7EDbSO6VYY8yblr3LscX0mlQtLjo46PxXsXCpFLf8M4kuR99rR
/6rc7N1pJF70tW4z1YtzoIpl4c1wAf9+6Qg2GJ3A2vxNtvtiSJ94kjYCEII/1cUe
u68llw8vSMaqQjjQFrLMn5dzIL1r6u2qD2S1FivtYgIF1V5i3Dga
=T2Kw
-----END PGP SIGNATURE-----

--Sig_/u=TtxToWBmbcUfvfDUO5Iii--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170528180919.7821e484>