Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 03 May 2022 15:27:33 +0200
From:      Jan Beich <jbeich@FreeBSD.org>
To:        Frank Seltzer <frank_s@bellsouth.net>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: Firefox 100.0_1,2 immediate crash on signal 5
Message-ID:  <pmku-g30a-wny@FreeBSD.org>
In-Reply-To: <20220503053032.3d8f89ea@Ace.nina.org> (Frank Seltzer's message of "Tue, 3 May 2022 05:30:32 -0400")
References:  <20220503053032.3d8f89ea.ref@Ace.nina.org> <20220503053032.3d8f89ea@Ace.nina.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Frank Seltzer <frank_s@bellsouth.net> writes:

> Upgrading to the latest version of Firefox results in the following
> errors and a crash in 10-15 seconds.  What am I missing?
>
> Thanks.
>
> console.warn: SearchSettings: "get: No settings file exists, new
> profile?" (new NotFoundError("Could not open the file at
> /home/frank_s/.mozilla/firefox/aksntfbh.default-release/search.json.mozlz4",
> (void 0))) JavaScript error: resource://gre/modules/XULStore.jsm, line
> 66: Error: Can't find profile directory. JavaScript error:
> resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile
> directory. console.warn: services.settings: Could not determine network
> status. Message: TypeError: Cc[aContract] is undefined Exiting due to
> channel error. Exiting due to channel error. Trace/BPT trap (core
> dumped)

Try rebuilding without LTO. rust-1.60 emits LLVM 14 bytecode that LLD
from llvm13 may not understand. firefox cannot switch to llvm14 yet
due to missing wasi-compiler-rt14. In the past firefox build usually
broke due to LLVM mismatch, so quickly noticed during exp-run.

Note, this was briefly discussed in https://reviews.freebsd.org/D34823
Note2, /quarterly (2022Q2) is NOT affected because it still has rust-1.59.



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