Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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 for Android 37.0 & 38.0 crash on startup

more options

Firefox for Android version 36.0 was working fine. When I upgraded to 37.0 the application began to crash a second or two after startup. On any given site.

I tried to erase the application data but it did no fix the problem durably. I was able to browse a page or two but after firefox synch was able to download my data on the device, the crashes restarted. I submitted numerous crash report through the included reporting tool.

Upgrading to version 38.0 did not fix the issue.

I don't even know how to figure what is causing the crash and therefore can't provide meaningful information for a bug report.

Edit: as per Philipp request : I'm using a Moto X+1 (aka "X 2nd gen." or whatever the marketing people decided to call it), Android version is 5.0.

Firefox for Android version 36.0 was working fine. When I upgraded to 37.0 the application began to crash a second or two after startup. On any given site. I tried to erase the application data but it did no fix the problem durably. I was able to browse a page or two but after firefox synch was able to download my data on the device, the crashes restarted. I submitted numerous crash report through the included reporting tool. Upgrading to version 38.0 did not fix the issue. I don't even know how to figure what is causing the crash and therefore can't provide meaningful information for a bug report. Edit: as per Philipp request : I'm using a Moto X+1 (aka "X 2nd gen." or whatever the marketing people decided to call it), Android version is 5.0.

Edeziri site na thcourbon

Asịsa ahọpụtara

After a few days, I reactivated Firefox Synch and have not experienced crash from then. It seems fixed...

Thank you for your help.

Cheers, Thomas

Gụọ azịza a na nghọta 👍 0

All Replies (7)

more options

hello, what device and software version of android are you using?

more options

I updated the question : Android 5.0 on Motorola X+1 (X 2n gen.)

more options

do the crashes continue when you clear the application's data but don't reconnect firefox to your sync account yet (or as soon as you link it to your account)?

Edeziri site na philipp

more options

I erased the application using Android builtin application managzr from the settings app.

So far no crash, I'm typing from Firefox for android in the incriminated device. The fun part is that it remember some (all ? I dunno) of my login/password even if I haven't not re-enabled Synch...

I'll keep using it a bit longer before synching again to be sure it no longer crashes.

I'll keep you posted. Thank for your help.

more options

thank you, i've also filed a bug for what i believe is the crash you were running into: https://bugzilla.mozilla.org/show_bug.cgi?id=1164449 (though i'm not sure, since if your firefox is crashing at startup there is no easy way to get to the crash signature of that particular problem...)

more options

Asịsa Ahọpụtara

After a few days, I reactivated Firefox Synch and have not experienced crash from then. It seems fixed...

Thank you for your help.

Cheers, Thomas

more options

I have experienced the same thing,also on 2014 moto x. Crash within a few seconds of startup. Clearing data relieved things for a while, but the problem came back. Haven't yet tried not connecting sync after clearing data; will try that now, but due to travel may not be able to report results for done time. FWIW, another Android device (and some windows ones) on the same sync account have no trouble.