From nobody Fri Aug 19 09:02:43 2022 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4M8G4C6SWjz4YV76 for ; Fri, 19 Aug 2022 09:02:51 +0000 (UTC) (envelope-from SRS0=ET07=YX=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4M8G4B5VwTz3lDw for ; Fri, 19 Aug 2022 09:02:50 +0000 (UTC) (envelope-from SRS0=ET07=YX=klop.ws=ronald-lists@realworks.nl) Date: Fri, 19 Aug 2022 11:02:43 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1660899763; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=dZ102JSIIxORM1+CxbWMGnpP2CF384wRE8x+u53sILg=; b=vpxYp7NYmVTCSVruTMmH4nWtvxjmI0S1loT8caoOnUxlpnlwok1rMYCdG1kUlFh7/iqoFU x76zJYJDFzloUEHbx76RowvcMAqwG17T8mWhrLX6pD/wy8Qm8tlON1TOp5CHPVZPXg6dpL 7l9xAAtD5bnWtx6Bn5LFTF3Wprut1TidOWFvSCmnpSgajvMQG+2vl9lm7fVYOjRAo4LIxS Y6ISE7SqqwQsl/lwY6iLp1FabQw+Ga03x3ixoq7OX6k1BOnSC64oo0UgQqreiTOz7N0WYw VPogaLQNuE9WNvp5SYT/vylN+jWcRZmcJcZQ4MrL6Ct+G73WByiMeNxhDonGYg== From: Ronald Klop To: ports@freebsd.org Message-ID: <14930703.74.1660899763480@localhost> In-Reply-To: References: Subject: Re: firefox-104.0,2 crashing List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_73_732237570.1660899763410" X-Mailer: Realworks (620.112) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4M8G4B5VwTz3lDw X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b=vpxYp7NY; dmarc=pass (policy=quarantine) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of "SRS0=ET07=YX=klop.ws=ronald-lists@realworks.nl" designates 194.109.157.24 as permitted sender) smtp.mailfrom="SRS0=ET07=YX=klop.ws=ronald-lists@realworks.nl" X-Spamd-Result: default: False [-3.20 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_LONG(-1.00)[-0.998]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; MID_RHS_NOT_FQDN(0.50)[]; FORGED_SENDER(0.30)[ronald-lists@klop.ws,SRS0=ET07=YX=klop.ws=ronald-lists@realworks.nl]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_ZERO(0.00)[0]; MLMMJ_DEST(0.00)[ports@freebsd.org]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; FROM_HAS_DN(0.00)[]; HAS_X_PRIO_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; FROM_NEQ_ENVFROM(0.00)[ronald-lists@klop.ws,SRS0=ET07=YX=klop.ws=ronald-lists@realworks.nl] X-ThisMailContainsUnwantedMimeParts: N ------=_Part_73_732237570.1660899763410 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Hi, What I find interesting from this mail thread and all follow up emails is t= hat there is no indication that the original problem has anything to do wit= h the ~/.Xauthority and /etc/hosts solution of the other person. There can be so many causes of a signal 11. What Nuru needs to do is run a debugger on the firefox.core file and try to= get a stacktrace of the error. >From the top of my head: $ lldb --core --file /usr/local/bin/firefox > bt You might need to recompile firefox with DEBUG option enabled to get any se= nsible output of the debugger. I don't have a lot of experience debugging f= irefox. NB: What version of FreeBSD are you running? Send the output of: uname -a Regards, Ronald. =20 Van: DtxdF Datum: woensdag, 17 augustus 2022 21:39 Aan: ports@freebsd.org Onderwerp: Re: firefox-104.0,2 crashing >=20 > Hello, >=20 > I have had the same problem. The problem is not only with firefox, it is = also valid with thunderbird in my experience. >=20 > I have debugged a bit using truss(1) and identified that the ~/.Xauthorit= y file and /etc/hosts is the problem. Actually, the problem is firefox and = thunderbird, but the initiators are them. >=20 > Check what display-names are displayed with `xauth list`. If you see a di= splay name as an invalid host in /etc/hosts, simply remove it with `xauth r= emove`. >=20 > My problem is that I changed the hostname, and it stayed after a firefox = upgrade, so I had two entries with an invalid hostname and a valid hostname= in .Xauthority. >=20 > See also /etc/hosts to see if there is an invalid host or check if you do= not have any entries where a host (such as your hostname) is missing. > =20 > El 17 de agosto de 2022 4:55:20 p. m. UTC, Nuno Teixeira escribi=C3=B3:>>=20 >> Hello to all, >> =20 >> Is anyone experience firefox crashes? For a long time that I did not see= so many crashes. >> It core dumped to firefox.core, can I do something usefull with .core to= get an ideia of what is causing it? >> =20 >> "pid 28063 (firefox), jid 0, uid 1001: exited on signal 11 (core dumped)= " >> =20 >> Cheers, >> -- >> Nuno Teixeira >> FreeBSD Committer (ports) >=20 ------=_Part_73_732237570.1660899763410 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi,

What I find interesting from this mail thread and all follow up emails is that there is no indication that the original problem has anything to do with the ~/.Xauthority and /etc/hosts solution of the other person.

There can be so many causes of a signal 11.

What Nuru needs to do is run a debugger on the firefox.core file and try to get a stacktrace of the error.

>From the top of my head:

$ lldb --core <path-to/firefox.core> --file /usr/local/bin/firefox
> bt

You might need to recompile firefox with DEBUG option enabled to get any sensible output of the debugger. I don't have a lot of experience debugging firefox.

NB: What version of FreeBSD are you running? Send the output of: uname -a

Regards,
Ronald.

 

Van: DtxdF <DtxdF@riseup.net>
Datum: woensdag, 17 augustus 2022 21:39
Aan: ports@freebsd.org
Onderwerp: Re: firefox-104.0,2 crashing

Hello,

I have had the same problem. The problem is not only with firefox, it is also valid with thunderbird in my experience.

I have debugged a bit using truss(1) and identified that the ~/.Xauthority file and /etc/hosts is the problem. Actually, the problem is firefox and thunderbird, but the initiators are them.

Check what display-names are displayed with `xauth list`. If you see a display name as an invalid host in /etc/hosts, simply remove it with `xauth remove`.

My problem is that I changed the hostname, and it stayed after a firefox upgrade, so I had two entries with an invalid hostname and a valid hostname in .Xauthority.

See also /etc/hosts to see if there is an invalid host or check if you do not have any entries where a host (such as your hostname) is missing.
 
El 17 de agosto de 2022 4:55:20 p. m. UTC, Nuno Teixeira <eduardo@freebsd.org> escribió:
Hello to all,
 
Is anyone experience firefox crashes? For a long time that I did not see so many crashes.
It core dumped to firefox.core, can I do something usefull with .core to get an ideia of what is causing it?
 
"pid 28063 (firefox), jid 0, uid 1001: exited on signal 11 (core dumped)"
 
Cheers,
--
Nuno Teixeira
FreeBSD Committer (ports)
------=_Part_73_732237570.1660899763410--