with the reason as “MozCrashReason: MOZ_CRASH(OOM)”
Anyone else seeing this?
Reverting back to FF 70.0.1 (with a saved 70.0.1 profile) and all is OK again, for the moment I’ve locked FF at 70.0.1 and am holding off updating my other TW install.
I normally run firefox on Leap 15.1. But I started it on Tumbleweed (in a VM), and it ran fine. This was with a relatively new profile (created in November).
Hmm… Thanks… Yes, I’ve updated a couple of Leap 15.1 installs to FF 71.0 and they both start and run fine.
I don’t have too much time right this moment, I’ll investigate more fully tomorrow. The TW machine’s both have new(ish) profiles also, but it could be a profile issue, or extension perhaps, although FF on the Leap machines have the same extensions as TW. :\
A quick “google” came up with a few *buntu users with similar problems, but that was on the beta release of FF…
I’m having the same problem, and it seems to be a widespread issue since several users on reddit are reporting it. For me crashes even with a new profile. For the moment the “solution” is to downgrade to FF70. You’ll need to run firefox with
Indeed it does the same with a new profile, I tried deleting ~/.cache/mozilla and temporarily renaming ~/.mozilla and upon start FF still crashes. Updated a second TW machine to FF 71.0 and the same issue, as I wrote earlier I’ve two Leap 15.1 systems and they’re fine with FF 71.0…
I’ve reverted both TW systems to 70.0.1 (using a restored profile, so no need for the “MOZ_ALLOW_DOWNGRADE”)