Hi,

On Wed, Jan 29, 2025 at 07:09:52AM +0900, Mike Hommey wrote:
> On Tue, Jan 28, 2025 at 02:10:45PM +0900, Mike Hommey wrote:
> > On Tue, Jan 28, 2025 at 04:41:26AM +0100, Sebastian Reichel wrote:
> > > Package: firefox
> > > Version: 134.0.2-2
> > > Severity: important
> > > X-Debbugs-Cc: Mike Hommey <gland...@debian.org>, Sebastian Reichel 
> > > <s...@debian.org>
> > > 
> > > Hi,
> > > 
> > > I see a lot of tab crashes with Debian's firefox binary on arm64 based
> > > T14s Gen6 Snapdragon. Usually when starting firefox or opening a new tab
> > > I am greeted with the tab crash reporter. After a few tries a page is
> > > actually rendered, so its not 100% broken. But with 80% crashes it is
> > > more or less unusable. The same setup on amd64 runs fine and the crashes
> > > also happen in safe mode / without a profile.
> > > 
> > > Apparently there is no firefox arm64 version in flathub, but I tried the
> > > librewolf 134.0.2 fork from there and I haven't seen a single crash with
> > > that. This suggests the crashes are somehow specific to the Debian
> > > version.
> > > 
> > > I used minidump-stackwalk as suggested by the firefox project to get
> > > a stacktrace for a few of the dmp files generated by firefox and it
> > > always seems to be due to SIGILL originating from locked_profiler_start
> > > as in the following output from minidump-stackwalk.
> > 
> > The SIGILL is actually happening in libgcc_s.so.1, and the faulting
> > instructions is autia1716. I'm not sure how much Firefox is at fault
> > here. The "good" news, at least, is that I can reproduce in a VM on
> > a mac.
> 
> Here is a workaround:
> - go to about:config
> - in the search field, search for "phc"
> - flip "memory.phc.enabled" to false

I can confirm, the huge amount of crashes is gone with that option.
Thanks!

-- Sebastian

Reply via email to