Firefox for Android Support Forum

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

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

So usually ill be playing a youtube video, and eventually the frames will stop and then firefox will crash, with the

Sorry Firefox crashed error

Now i just got a new Tablet my partner was using with no crashes and im crashing on that too, so it could be an account issue?

Already tried clearing cache and data and having no Addons Any help would be appreciated :)

Hi,

We use about ten Android tablets running Firefox in our shop for our employees to enter on a webpage daily some informations. Tablets are programmed to keep display active 24h/7d, firefox is pinned so the app stay opened and users don't go to other app. The extension LeechBlock NG prevent users from accessing other webistes. Everything work well except on mondays morning.

Without fault first person to try to connect on the website will see the app crash to the desktop. Since the app is pinned user will have to wait for a supervisor to come in and unpin the crashed (and invisible) app, re-launch it and pin it. Then it will work all week without issue as long as the tablet is used at least once a day. We recently added a new tablet which is used less than others and that one does crash during the week but never twice in same day. Here's the crash report that we have (I checked multiples tablets and they all share the same crash code):

99526033-8b07-4d48-9ea2-bf4b81157f56 mozilla.appservices.places.uniffi.PlacesApiException$UnexpectedPlacesException: reason=Invalid metadata observation: Observed view time is invalid (too long)

mozilla.appservices.places.uniffi.PlacesApiException$UnexpectedPlacesException: reason=Invalid metadata observation: Observed view time is invalid (too long)

at mozilla.appservices.places.uniffi.FfiConverterTypePlacesApiError.read(places.kt:21)
at mozilla.appservices.places.uniffi.FfiConverterTypePlacesApiError.read(places.kt:1)
at mozilla.appservices.places.uniffi.FfiConverter$DefaultImpls.liftFromRustBuffer(places.kt:13)
at mozilla.appservices.places.uniffi.FfiConverterRustBuffer$DefaultImpls.liftFromRustBuffer(places.kt:6)
at mozilla.appservices.places.uniffi.FfiConverterTypePlacesApiError.liftFromRustBuffer(places.kt:2)
at mozilla.appservices.places.uniffi.FfiConverterTypePlacesApiError.liftFromRustBuffer(places.kt:1)
at mozilla.appservices.places.uniffi.FfiConverterRustBuffer$DefaultImpls.lift(places.kt:7)
at mozilla.appservices.places.uniffi.FfiConverterTypePlacesApiError.lift(places.kt:3)
at mozilla.appservices.places.uniffi.FfiConverterTypePlacesApiError.lift(places.kt:2)
at mozilla.appservices.places.uniffi.PlacesApiException$ErrorHandler.lift(places.kt:2)
at mozilla.appservices.places.uniffi.PlacesApiException$ErrorHandler.lift(places.kt:1)
at mozilla.appservices.places.uniffi.PlacesConnection.noteHistoryMetadataObservation(places.kt:162)
at mozilla.appservices.places.PlacesWriterConnection.noteHistoryMetadataObservation(PlacesConnection.kt:19)
at mozilla.components.browser.storage.sync.PlacesHistoryStorage$noteHistoryMetadataObservation$2.invokeSuspend(PlacesHistoryStorage.kt:63)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:107)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
Suppressed: kotlinx.coroutines.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@57af652, java.util.concurrent.Executors$FinalizableDelegatedExecutorService@1d40d23]

Wondering if someone can help me decypher this to fix/prevent it. Is it the extension or browser itself that cause the crash if the page hasn't changed long enough? Thanks for suggestions (I will not consider "have you tried without the extension" as a valid suggestion)

Just updated to latest version of Firefox for Android (ver 113). When I try to watch a YouTube video in full screen, the app suddenly closes, as if I pressed the home button (note: I say "close" rather than "crash" because when I reopen it, all the pages are still loaded). This doesn't happen every time, but it is annoying. Is there any way to fix this?

For months now, Firefox Mobile has constantly been getting "app has stopped responding" crashes and even hard crashes (multiple times per day) for Pixel users. There's already a bug report about it but the FF team's response is that they aren't going to do anything. They claim it's an issue with the kernel but no other apps / browsers on the Pixel have this problem.

This is beyond pathetic. Maybe this not-my-problem mentality is why Firefox has reduced to less than 1% penetration.

When attempting to enter full screen mode on Firefox for Android, and to get into landscape mode, the browser appears to crash, keeps audio playing, and "entering full screen mode" dialogue pops up. Have to open Firefox again, and can only be viewed in landscape mode while session is continued. To return to non-landscape mode, the app needs to be force stopped, otherwise you only get to see the left one third side of any web page you navigate to. Seems to have started with most recent update. Is there any way to fix?

So on my main firefox account the app crashes after a few mins consistently, on my phone and Tablet.

However I recently made a different account using a different email adress and zero crashes.

Is it likely to be a settings issue?

I raised this issue in my review on the Google App Store and was asked to submit it as a question here. On my phone (Oppo running on ColorOS 13.1), Firefox will stop working a number of times a month. For about 24 hours, aside from Google result pages, nothing will load, and I'll be stuck looking at an empty loading screen. The last time I raised this issue I was told to delete and reinstall the app, which worked in the moment but did nothing to stop the problem occurring again. Aside from waiting for the app to fix itself, nothing I've found works.

Firefox Android just crashed when opening a bunch of bookmarks and then again every time I wanted to report a crash. I hope someone here can forward this to whoever usually receives the crash reports.

1cb54f1f-11f5-4fa7-9d97-b4bf58d29ac2 java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String java.lang.Object.toString()' on a null object reference

java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String java.lang.Object.toString()' on a null object reference at java.lang.String.valueOf(String.java:2924) at java.lang.StringBuilder.append(StringBuilder.java:132) at java.lang.Throwable.printEnclosedStackTrace(Throwable.java:709) at java.lang.Throwable.printStackTrace(Throwable.java:674) at java.lang.Throwable.printStackTrace(Throwable.java:735) at mozilla.components.support.base.ext.ThrowableKt.getStacktraceAsString$default(Throwable.kt:19) at mozilla.components.lib.crash.service.MozillaSocorroService.sendCrashData(MozillaSocorroService.kt:607) at mozilla.components.lib.crash.service.MozillaSocorroService.sendReport$lib_crash_release(MozillaSocorroService.kt:285) at mozilla.components.lib.crash.service.MozillaSocorroService.report(MozillaSocorroService.kt:5) at mozilla.components.lib.crash.CrashReporter$submitReport$2.invokeSuspend(CrashReporter.kt:70) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:112) at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:4) at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:3) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:96) Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@6aec4f8, Dispatchers.IO]

The original bookmarks crash was this:

300e77b6-00e5-458d-ae84-d1202c866a1b java.lang.NullPointerException

* New Sentry Instance: https://sentry.io/organizations/mozilla/issues/?project=6375561&query=9fd75a9f565c460b91e4977064d87e83

java.lang.NullPointerException at org.mozilla.fenix.library.bookmarks.BookmarkFragment.refreshBookmarks(BookmarkFragment.kt:103) at org.mozilla.fenix.library.bookmarks.BookmarkFragment$refreshBookmarks$1.invokeSuspend(BookmarkFragment.kt:14) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:112) at android.os.Handler.handleCallback(Handler.java:883) at android.os.Handler.dispatchMessage(Handler.java:100) at android.os.Looper.loop(Looper.java:214) at android.app.ActivityThread.main(ActivityThread.java:7400) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:935) Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@26f4bf6, Dispatchers.Main]

I've been using Firefox on my phone for about half a year, rarely updating the browser. I did it first time approximately 2 weeks ago and since then it started to crash frequently. The latest update hasn't resolved the issue.

Setup: - galaxy S23+ - latest Android version (13) - Firefox version 121.0.1 (Build #2015995071), fd4d251332+ GV: 121.0.1-20231230165955 AS: 121.0

I have more than 100+ tabs opened with a setting activated "Close tab: Never" and "Move old tabs to inactive". Has several plugins installed: - Ghostery - Decentraleyes - Search by Image - uBlock Origin - ClearURLs

I usually visit 5-10 websites a day, having multiple opened tabs to read later. Sometimes when I open a new tab, open the page, start scrolling, the browser slows down and then crashes. It doesn't show any error, just shuts down the app so I have to open it again.

firefox is crashing when i try to download some file. I gotta clear the app's data for it to work normally again, but this always happens when I try to download it again, also, the browser doesn't open after it crashes, only after I clear its data.

Firefox for Android version 119.0.1 Android 11 (64 bits)

Sometimes whenever i use twitter it will crash and stop working everytime i switch a other tab it glitches and stays on the tab i switched from, and it would also black out and make the tab unusable.

Hi support team,

I was using Mozilla Firefox on my Samsung Galaxy s20+ without any issues. I have transferred all data from my old one to new one, Samsung Galaxy S24 after this migration Mozilla Firefox crashes, when I was forwarded from an app.

Standard browser: Mozilla Firefox I have already reinstalled the Mozilla. This action works properly with other browsers.

Kind regards Mustafa

Very often when clicming the adress bar (almost always on sites like old.reddit.com, the app just stops responding and I must reopen it. I'd like a solution that won't involve removing all my bookmarks, history and saved data.

i am badly facing the unexpected shutdowns issues on my website about call girl in bangalore rajajinagar i have checked the following issues but still not solved? Conflict with other software or programs running on the computer.

Corrupted or outdated browser or system files.

Insufficient system resources, such as memory or storage.

Issues with the browser's profile or settings.

Conflicting add-ons or extensions.

Outdated graphics drivers.

Malware or viruses.

Corrupted or outdated browser extensions.

Conflicting third-party software.

Network connectivity issues.

Firefox has been crashing my phone for a while now. It finally was able to generate a crash log. Can someone take a look at the log and see what might be causing it? Thanks.

https://crash-stats.mozilla.org/report/index/32b12d52-cee0-49a4-bc70-7fea40230419#tab-rawdump

Old thread talking about the crash if anyone's interested.

https://support.mozilla.org/en-US/questions/1408791

My phone is on Android 13 with the latest Firefox update. Under "Crashes" in Settings, there isn't much.

Here's a video: https://imgur.com/a/7etdWuL