Firefox for Android Support Forum

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?

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?

When reading the site https://hellasjournal.com after a while Firefox freezes and crashes. It's not a site problem because with Chrome works fine.

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

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

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?

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 :)

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.