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 keeps crashing since update to Android 14

  • 10 replies
  • 3 have this problem
  • 3 views
  • Last reply by pnobre3

more options

Hi,

Since I've installed the latest Samsung OneUI6/Android 14, Firefox keeps crashing randomly. There was a firefox update after (120.1.0, build #2015989146), but same behavior. When opening accessing a new url (either new tab or existing tab). No message displayed, simply closes. Everything is up to date, non rooted galaxy S23 ultra with Android 14/OneUI 6. Already cleared firefox app cache, uninstalled and reinstalled (this worked for a few hours, but it's back to same behavior).

Any ideas?

P

Hi, Since I've installed the latest Samsung OneUI6/Android 14, Firefox keeps crashing randomly. There was a firefox update after (120.1.0, build #2015989146), but same behavior. When opening accessing a new url (either new tab or existing tab). No message displayed, simply closes. Everything is up to date, non rooted galaxy S23 ultra with Android 14/OneUI 6. Already cleared firefox app cache, uninstalled and reinstalled (this worked for a few hours, but it's back to same behavior). Any ideas? P

All Replies (10)

more options

Hi

I am sorry to hear that Firefox for Android is crashing. I hope that we can help resolve this for you. Before following the steps below, make sure that you have updated both your Android device and Firefox for Android to the latest versions available.

As a first step, close down many of the tabs that you have open to as few as possible. Does this help reduce the incidence of a crash?

If this does not resolve the issue, open the Android Settings app, select Applications then find Firefox in the list. In the section headed "Storage", selct the option to clear the cache (do not clear data!). Does this help?

Failing that, our developers will need to look into this in more detail with some logs from inside your copy of Firefox for Android. Type about:crashes in the address bar which will display information about recent crashes. If you select the most recent "Socorro" link, a crash report will open in a new tab. If you could copy and paste the address of the page that opens into a reply to this thread, we will be able to look into this further for you.

I hope that this helps.

more options

Hi,

As I've mentioned, I had emptied the app cache before resorting to uninstalling and installing the app again. I used to have usually 100+tabs open (useful :-), and that's my average across each device) but just synched all of them on a different device before uninstalling (and they all went away). There are no crash reports (about:crashes just says "no crash reports submitted) as firefox simply stops, no messages presented. Let me know if there's any more info I can provide. I haven't been able yet to see a pattern for it crashing, for now, everything seems to be quite random.

P

more options

Can you check to see if 'Enable Firefox Suggest' is toggled on in Secret Settings? You can unlock the Secret Settings page by going to Settings -> About Firefox -> tap on the logo at the top 5 times.

If it is on, can you turn it off and see if that improve your situation?

more options

It's disabled.

more options

Okay. Please can you enable it, close Firefox for Android, reopen Firefox for Android and disable it.

Does that help?

more options

Seeme to be holding on after doing this... will keep observing and reporting here.

P

more options

Hi

Is everything working okay now?

more options

Hi there,

Haven't used the phone a lot if the past few days, but it still presented the same behavior a couple of times.

Thanks, P

more options

My honest opinion is that Android 14 and all of Samsung do not know how to follow any commands properly. Does anybody agree? BlackBerry is much better.

more options

After last samsung update (Dec security patch level) things gotten worse. Trying out a new theory, switched from duckduckgo as default search engine to google (ughhh) and see if it helps as I've noticed most of the crashes happen when tipping a url (probably unrecognized, leading to a ddg search query) or search term on the address bar....