为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Firefox Android Crashes - java.lang.OutofMemoryError

  • 12 个回答
  • 3 人有此问题
  • 1 次查看
  • 最后回复者为 Skulljeep

more options

Hello,

I am getting a frequent freeze in the Android app and then shortly after a crash. Info: - happens on FF, FF Beta, and FF Nightly,and reinstall/phone reset didn't fix. - Samsung Galaxy SM-G965U running Android 10. - every error starts with java.lang.OutofMemoryError. - it never happens just on startup, just on auto fill, or some of the similar crash reports I've seen around here. - it does appear to be site-specific, but sometimes the site works and sometimes it does not: if I close the last tab after a crash, it will usually work for awhile. - Sync and disabling Add-ons doesnt fix it, although perhaps its worse with uBlock Origin enabled (not conclusively)

Thanks for any suggestions.

edited for clarity

Hello, I am getting a frequent freeze in the Android app and then shortly after a crash. Info: - happens on FF, FF Beta, and FF Nightly,and reinstall/phone reset didn't fix. - Samsung Galaxy SM-G965U running Android 10. - every error starts with java.lang.OutofMemoryError. - it never happens just on startup, just on auto fill, or some of the similar crash reports I've seen around here. - it does appear to be site-specific, but sometimes the site works and sometimes it does not: if I close the last tab after a crash, it will usually work for awhile. - Sync and disabling Add-ons doesnt fix it, although perhaps its worse with uBlock Origin enabled (not conclusively) Thanks for any suggestions. edited for clarity

由kBayi于修改

所有回复 (12)

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

Thanks for the response.

It has crashed with only one tab open, so I don't think that's it. Phone software and app software are up to date (installed with Google Play). I have tried clearing the cache and no luck.

Here's an error report link https://crash-stats.mozilla.org/report/index/05818aa6-63f4-4a36-ab36-cd9420231114

more options

That crash report if empty, so no useful data is available. Did you try to close as many apps as possible to give more memory space to Firefox ?

more options

That's the most recent with a link. One from yesterday looks like: java.lang.OutOfMemoryError: Failed to allocate a 16 byte allocation with 503240 free bytes and 491KB until OOM, target footprint 268435456, growth limit 268435456; failed due to fragmentation (largest possible contiguous allocation 257687552 bytes)....if I get another one I'll look for a report link and post that.

Re: tabs, yes, I have had it crash with just one tab (all other closed) open. I've also had it run for several days no crashes with 20+ tabs.

I also don't usually leave a lot of background apps open except the ones that run in the background anyway, for what that's worth.

I've been trying to sus out a pattern of maybe which sites it crashes on most / see if they have similar elements, but I don't have a hypothesis yet.

more options

Latest one:

https://crash-stats.mozilla.org/report/index/7fd6e357-5c0f-41ac-9e76-65e2c0231118#tab-details

Different error than last time / this one occurred when opening an outside link (from Gmail or some other app) - immediate crash. If anyone thinks this needs a different thread b/c it's a different error, that's fine.

Edit: more recent one duplicating the original experience:

https://crash-stats.mozilla.org/report/index/bp-94987862-94e1-4781-add7-8f2e50231120

由kBayi于修改

more options

And I suppose this has been abandoned, but one more for anyone curious:

https://crash-stats.mozilla.org/report/index/53b50a4a-dc24-4399-80e1-d684e0231123

more options

Hi

Which other apps do you have running when this happens?

more options

Usually only apps that are regularly open are Google's Calendar and Gmail. Nothing that has a huge memory toll (no games, Youtube, etc). I usually close apps out when I'm done with them. Firefox is the only that crashes.

more options

It appears that you are using the Nightly build of Firefox for Android. Does that same thing happen in the Release version? Do you have a Release crash report?

more options

Yep, that was mentioned in the original post; here's latest crashes on the Release application:

https://crash-stats.mozilla.org/report/index/7d0dd8a8-8f98-4d35-8f3d-1731d0231120

https://crash-stats.mozilla.org/report/index/1eef37be-c1b4-402e-9996-b08ce0231125

If this is unresolvable, fine: I'd just like to know that before I hop to another browser permanently. If there is an easy fix (other than to never run more than one application / more than one tab), then I'm happy to try to implement.

(edited: fixed broken links - c)

由cor-el于修改

more options

Hi

Please can you check for updates to Firefox for Android. We have release version 120.1 that may resolve the issue that you are experiencing.

由Paul于修改

more options

I have the same problem but on another device. It's clearly a coding issue for the app. Because for my Samsung Galaxy S20 Ultra +5G I have no issues with any other browser. Just Firefox as the only failure. I'm about to transfer back to Chrome at this point because there is no fix for this bad update.