Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox Mobile 18a1 crashes all the time

  • 2 balasan
  • 3 ada masalah ini
  • 3 paparan
  • Balasan terakhir oleh Craig

more options

I have been testing Nightly builds of Firefox Mobile for Android for some time now. Recently (after Ion landed), the browser crashes all the time. I can't even get into about:config or about:crashes long enough to get any useful information or try anything. Is there a way to put the browser in Safe Mode? Any other ideas?

Samsung Galaxy Nexus CyanogenMod 10 (Nightly) (Android 4.1.1)

and

HP TouchPad CyanogenMod 9 (Android 4.0.3)

I have been testing Nightly builds of Firefox Mobile for Android for some time now. Recently (after Ion landed), the browser crashes all the time. I can't even get into about:config or about:crashes long enough to get any useful information or try anything. Is there a way to put the browser in Safe Mode? Any other ideas? Samsung Galaxy Nexus CyanogenMod 10 (Nightly) (Android 4.1.1) and HP TouchPad CyanogenMod 9 (Android 4.0.3)

Diubah oleh Craig

All Replies (2)

more options

Hey,

Yes, this is known. We've got a couple bug reports on file and have been investigating it this week. See bugs: http://bugzil.la/791781, http://bugzil.la/792342, http://bugzil.la/790139.

The crash you describe sounds like http://bugzil.la/790139 as I came across this too yesterday.

Hopefully we'll see some fixes soon.

more options

Thanks for the links Aaron. The crashes in CM10 are far worse than CM9 so far. I'm not using the Reader Mode to cause it to crash (though I do use that feature). It goes down after a couple of seconds at a lot of pages (about:config, about:crashes) without doing a single thing.

I noted that it started happening after Ion landed. I don't know for sure that it is Ion related. If I could keep about:config alive long enough to disable Ion, I would know pretty quickly if that is the problem. I don't know of any other significant changes to Firefox Mobile lately that could have caused this.