Starting 84.0b2 with either uBlock Origin or Firefox Multi-Account Containers enabled results in frequent / nearly-immediate crashes
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
People
(Reporter: bugzilla.mozilla.org, Unassigned)
References
Details
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/65232e79-26df-4401-bd84-46b9a0201119
I'm trying to set up a new "Apple Silicon" (ARM64) MacBook Air.
I'm having a lot of trouble getting uBlock Origin and Multi-Account Containers working together, issues that I'm not seeing on my Intel desktop; but I haven't yet narrowed that down to a report-able / reproducible test-case. In the process, though, I've discovered this very reproducible bug: that I can't install either of these addons on Firefox Developer Edition (84.0b2) or Nightly (85.0a1? I think?) without the browser basically becoming crash-on-launch.
(The exact timing of the crash varies, but it's very soon after starting — sometimes I can get a new-tab operation to complete, but not usually. It usually takes four or five launches to manage to get into the menu and hit "Restart with Add-ons disabled ..." successfully before it can crash, to even view about:crashes
, heh.)
Happy to provide more debugging efforts if there's something that can help!
Reporter | ||
Comment 1•4 years ago
|
||
I may be pulling this out of my butt — but it does look like this may be M1-related, as the graph of similar crashes seems to rocket up out of nowhere within the last week, which is exactly the time-period where people have begun to receive ARM64 / M1 Macs:
Similarly, almost 30% of them have the MacBook "graphics adapter" value of "Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X] (0x6810)":
Comment 2•4 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Comment 3•4 years ago
|
||
Hello,
I’ve attempted to reproduce the issue on the latest Nightly (85.0a1/20201122213806), Beta (84.0b4/20201122152513), Release (83.0/20201112153044) and Beta Developer Edition (84.0b4/20201122152513) under Windows 10 Pro, however without success.
Attempted reproduction on macOS 10.15 as well, however the used device does not have the new M1 chip (but an Intel) and the issue did not occur.
Comment 4•4 years ago
|
||
Hi ELLIOTTCABLE,
Can you please give it a try on the latest Firefox Beta 84.0b5 or the latest Nightly 85? Can't reproduce this on my side, using remote connection to a MacStadium DTK with the new Apple Silicon chip.
The only issue I see is on the latest Beta 84.0b5 where either uBlock or Multi-Account Container addon panel is not displayed or blank if both are installed, this is not reproducible on Nightly tho.
Reporter | ||
Comment 5•4 years ago
|
||
Confirmed, still reproducing on 85.0a1 2020-11-26:
https://crash-stats.mozilla.org/report/index/5c5589a8-1e30-43c0-90f7-3fac50201127
Still the case that disabling either addon seems to prevent the behaviour; also still the case that it's really difficult to reproduce reliably — this time, on Nightly 85.0a1, I was able to open Reddit, GitHub, Google, and Bugzilla, and browse around for a bit, with both enabled, before it finally "started crashing." Subsequent crashes were much quicker after attempting to relaunch the browser.
Reporter | ||
Comment 6•4 years ago
|
||
Additionally, it looks like other users have started to report this issue over on the uBlock tracker:
I have the same issue on Macbook Pro 13" M1 with uBlock Origin and Firefox Multi-Account Containers in 84.0b5.
For testing, I replaced "uBlock Origin" with "AdBlocker Ultimate", the bug still present.
No issue with Adblock Plus
Comment 9•4 years ago
|
||
Possibly related: https://bugzilla.mozilla.org/show_bug.cgi?id=1678226#c15
Comment 10•4 years ago
|
||
The severity field is not set for this bug.
:mixedpuppy, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 11•4 years ago
|
||
Version 84.0b8 looks have fixed the issues I have previously with Multi-Account Containers + 1password + uBlock.
No issue during the last 2 days.
Comment 12•4 years ago
|
||
Thanks for reporting back - it looks like bug 1678226 has fixed the issue.
Description
•