Цей вебсайт матиме обмежену функціональність, доки ми проводимо його обслуговування для поліпшення роботи. Якщо прочитана стаття не розв'язала вашу проблему і ви хочете поставити питання, наша спільнота підтримки з радістю допоможе вам на @FirefoxSupport у Twitter та /r/firefox на Reddit.

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

Frequent Crashes and high data use on Samsung S23+

  • 4 відповіді
  • 1 має цю проблему
  • 1 перегляд
  • Остання відповідь від Xarl

more options

I recently moved to a new phone, Samsung S23+ after being on a OnePlus phone for several years. My new phone is much beefier but has been suffering from frequent crashes (it actually just crashed as I was typing this part.)

The crashes all seem to be variations of:

284caa59-49ff-4df4-ae44-17afa3c49fa4 java.lang.OutOfMemoryError: Failed to allocate a 16 byte allocation with 1502304 free bytes and 1467KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC.


java.lang.OutOfMemoryError: Failed to allocate a 16 byte allocation with 1502304 free bytes and 1467KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC. at com.android.internal.inputmethod.InputConnectionCommandHeader$1.createFromParcel(InputConnectionCommandHeader.java:55) at com.android.internal.inputmethod.InputConnectionCommandHeader$1.createFromParcel(InputConnectionCommandHeader.java:51) at android.os.Parcel.readTypedObject(Parcel.java:4037) at com.android.internal.inputmethod.IRemoteInputConnection$Stub.onTransact(IRemoteInputConnection.java:445) at android.os.Binder.execTransactInternal(Binder.java:1380) at android.os.Binder.execTransact(Binder.java:1311)

I've tried the beta version of Firefox android, I've tried with and without add-ons, I'm not sure what else to try.

Something that I noticed and thought might be related is that I had 4.7GB of background mobile data usage over the past month. I tried turning off background data usage, but it is still crashing.

I recently moved to a new phone, Samsung S23+ after being on a OnePlus phone for several years. My new phone is much beefier but has been suffering from frequent crashes (it actually just crashed as I was typing this part.) The crashes all seem to be variations of: 284caa59-49ff-4df4-ae44-17afa3c49fa4 java.lang.OutOfMemoryError: Failed to allocate a 16 byte allocation with 1502304 free bytes and 1467KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC. ---- java.lang.OutOfMemoryError: Failed to allocate a 16 byte allocation with 1502304 free bytes and 1467KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC. at com.android.internal.inputmethod.InputConnectionCommandHeader$1.createFromParcel(InputConnectionCommandHeader.java:55) at com.android.internal.inputmethod.InputConnectionCommandHeader$1.createFromParcel(InputConnectionCommandHeader.java:51) at android.os.Parcel.readTypedObject(Parcel.java:4037) at com.android.internal.inputmethod.IRemoteInputConnection$Stub.onTransact(IRemoteInputConnection.java:445) at android.os.Binder.execTransactInternal(Binder.java:1380) at android.os.Binder.execTransact(Binder.java:1311) I've tried the beta version of Firefox android, I've tried with and without add-ons, I'm not sure what else to try. Something that I noticed and thought might be related is that I had 4.7GB of background mobile data usage over the past month. I tried turning off background data usage, but it is still crashing.

Усі відповіді (4)

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, please 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 Paul!

Thanks for responding. <3

I've tried closing tabs, clearing the Firefox cache, and the phone's cache partition as well as checking I'm on the latest, not beta, Firefox. I was getting these on the beta version as that's what I initially installed when I moved phones but I changed to the regular release after the crashes started happening.

I just got a crash now as I was closing some tabs that did produce a Soccoro link (not all of them do) https://crash-stats.mozilla.org/report/index/10149ff0-0f00-4b16-9256-3d15f0230930

I have also gotten a couple native crashes which may be related? Here's one as an example: https://crash-stats.mozilla.org/report/index/4bc270d4-011a-40df-8c35-2b4940230928

Let me know if there's anything else you'd like me to provide. :)

more options

Thank you for those links, really useful.

Do you have many other apps open on your Android device?

Do you have many tabs open or stored in Collections?

more options

Not many that I can tell, at most the same amount as I had on my old phone which didn't have this issue.

I have 7 tabs open at the moment but I've had it happen when I've only had one or two open.

I don't use Collections.