Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

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.

കൂടുതലറിയുക

Firefox keeps crashing on Samsung Galaxy Tab A8 with Android 14

  • 3 മറുപടികൾ
  • 0 have this problem
  • 31 കാഴ്ചകൾ
  • Last reply by Cajundweeb

more options

Have be3n hav8ng this problem for at least a week, on a Samsung Galaxy Tab A 8 with Android 14 (One UI). About 20cto 30 seconds after launch, the browser abruptly closes back to the home screen. Have tried resetting the tablet, clearing some old apps out, etc., but thr problem persists.

I have dumped the latest Mozilla Crash Report from my browser. Apparently, there is an issue with memory:

cf13ba46-8115-4130-8396-249e2c218304 java.lang.OutOfMemoryError: Failed to allocate a 134217744 byte allocation with 50331648 free bytes and 116MB until OOM, target footprint 129110320, growth limit 201326592


java.lang.OutOfMemoryError: Failed to allocate a 134217744 byte allocation with 50331648 free bytes and 116MB until OOM, target footprint 129110320, growth limit 201326592 at java.util.Arrays.copyOf(Arrays.java:3578) at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:120) at java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:95) at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:156) at kotlin.io.ByteStreamsKt.copyTo(IOStreams.kt:19) at kotlin.io.ByteStreamsKt.readBytes(IOStreams.kt:21) at mozilla.appservices.httpconfig.FetchBackend.sendRequest$lambda$3(FetchBackend.kt:6) at mozilla.appservices.httpconfig.FetchBackend.sendRequest(FetchBackend.kt:274) at mozilla.appservices.viaduct.uniffiCallbackInterfaceBackend$sendRequest$callback$makeCall$1.invokeSuspend(viaduct.kt:49) at mozilla.appservices.viaduct.uniffiCallbackInterfaceBackend$sendRequest$callback$makeCall$1.invoke(viaduct.kt:2) at mozilla.appservices.viaduct.uniffiCallbackInterfaceBackend$sendRequest$callback$makeCall$1.invoke(viaduct.kt:1) at mozilla.appservices.viaduct.uniffiCallbackInterfaceBackend$sendRequest$callback$$inlined$uniffiTraitInterfaceCallAsyncWithError$1.invokeSuspend(viaduct.kt:31) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:122) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:127) Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@e36b064, Dispatchers.Default]

Can SOMEONE help me figure this out, what should I do, etc.? I am going crazy fighting this..

Have be3n hav8ng this problem for at least a week, on a Samsung Galaxy Tab A 8 with Android 14 (One UI). About 20cto 30 seconds after launch, the browser abruptly closes back to the home screen. Have tried resetting the tablet, clearing some old apps out, etc., but thr problem persists. I have dumped the latest Mozilla Crash Report from my browser. Apparently, there is an issue with memory: cf13ba46-8115-4130-8396-249e2c218304 java.lang.OutOfMemoryError: Failed to allocate a 134217744 byte allocation with 50331648 free bytes and 116MB until OOM, target footprint 129110320, growth limit 201326592 ---- java.lang.OutOfMemoryError: Failed to allocate a 134217744 byte allocation with 50331648 free bytes and 116MB until OOM, target footprint 129110320, growth limit 201326592 at java.util.Arrays.copyOf(Arrays.java:3578) at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:120) at java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:95) at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:156) at kotlin.io.ByteStreamsKt.copyTo(IOStreams.kt:19) at kotlin.io.ByteStreamsKt.readBytes(IOStreams.kt:21) at mozilla.appservices.httpconfig.FetchBackend.sendRequest$lambda$3(FetchBackend.kt:6) at mozilla.appservices.httpconfig.FetchBackend.sendRequest(FetchBackend.kt:274) at mozilla.appservices.viaduct.uniffiCallbackInterfaceBackend$sendRequest$callback$makeCall$1.invokeSuspend(viaduct.kt:49) at mozilla.appservices.viaduct.uniffiCallbackInterfaceBackend$sendRequest$callback$makeCall$1.invoke(viaduct.kt:2) at mozilla.appservices.viaduct.uniffiCallbackInterfaceBackend$sendRequest$callback$makeCall$1.invoke(viaduct.kt:1) at mozilla.appservices.viaduct.uniffiCallbackInterfaceBackend$sendRequest$callback$$inlined$uniffiTraitInterfaceCallAsyncWithError$1.invokeSuspend(viaduct.kt:31) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:122) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:127) Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@e36b064, Dispatchers.Default] Can SOMEONE help me figure this out, what should I do, etc.? I am going crazy fighting this..

എല്ലാ മറുപടികളും (3)

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 Apps then find Firefox in the list. In the section titled Storage and Cache, select the option to clear the cache (do not clear data!). Does this help?

Following 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

Paul, here's the latest crash report:

b85eab69-a65f-485e-a392-6706dbce7309 java.lang.OutOfMemoryError: Failed to allocate a 134217744 byte allocation with 50331648 free bytes and 110MB until OOM, target footprint 135843216, growth limit 201326592


java.lang.OutOfMemoryError: Failed to allocate a 134217744 byte allocation with 50331648 free bytes and 110MB until OOM, target footprint 135843216, growth limit 201326592 at java.util.Arrays.copyOf(Arrays.java:3578) at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:120) at java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:95) at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:156) at kotlin.io.ByteStreamsKt.copyTo(IOStreams.kt:19) at kotlin.io.ByteStreamsKt.readBytes(IOStreams.kt:21) at mozilla.appservices.httpconfig.FetchBackend.sendRequest$lambda$3(FetchBackend.kt:6) at mozilla.appservices.httpconfig.FetchBackend.sendRequest(FetchBackend.kt:274) at mozilla.appservices.viaduct.uniffiCallbackInterfaceBackend$sendRequest$callback$makeCall$1.invokeSuspend(viaduct.kt:49) at mozilla.appservices.viaduct.uniffiCallbackInterfaceBackend$sendRequest$callback$makeCall$1.invoke(viaduct.kt:2) at mozilla.appservices.viaduct.uniffiCallbackInterfaceBackend$sendRequest$callback$makeCall$1.invoke(viaduct.kt:1) at mozilla.appservices.viaduct.uniffiCallbackInterfaceBackend$sendRequest$callback$$inlined$uniffiTraitInterfaceCallAsyncWithError$1.invokeSuspend(viaduct.kt:31) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:122) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:127) Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@5ce7e62, Dispatchers.Default]

I'm unable to access the Soccoroo page for this crash

more options

Just downloaded the latest update, and so far, it appears to be fixed.

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.