Форум сообщества Firefox для Android

Dear Mozilla support,

For a while I have the problem that when I want to watch a video fullscreen on a website e.g. youtube, inline video etc. Firefox stops and completely closes. This is only the first time when I play the video. When I re-open the browser I can continue watching the video fullscreen without any problem. I don't receive any error messages.

Attached the specs of my phone and Firefox browser.

Kind regards, Rick

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

Once a while Firefox would freeze up and when that happens it would without fail reboots the phone if the phone goes to sleep and if I don't force close the app quickly. It might've done so anyway without putting it to sleep but I haven't tested leaving the screen on long enough. I noticed that if I was quick enough and force stop the app the phone doesn't reboot, but that window is really short. Maybe 2 seconds or so. Suffice to say force stopping didn't always work since the window is so short. When Firefox freezes other apps and phone functions work normally. It's been ongoing for a while through multiple updates. I see some people have already reported this same issue here. Can Mozilla fix this please? I have uBlock origin addon installed thanks. Also this never happened with my Pixel 3 phone which I was using up until a few months back so maybe it's pixel 6a specific. Alot of people have this same issue with pxiel6a from googling. It can freeze on any site I visit but one example is reddit.

I have a Blackview Tab16 (10" screen), which I bought last year; it was running Firefox quite happily until a couple of months ago. Now when I click on the icon, I get a sort of 'welcome' screen (with some message about a search widget?) for a fraction of a second, then FF closes and I get an error message saying 'Sorry. Firefox had a problem and crashed.' The version of FF is 126.0. I was told to try clearing the cache, but there is nothing there to clear! The tablet is running Android 12 / DoKe OS V3.0.

I have an 8" Blackview tablet which - despite needing to be plugged in to run all the time! - opens & runs Firefox perfectly happily. It's my main browser on my MacBook as well, and will run on my iPhone.

Steps to reproduce : - go to YouTube - open a video - press the full screen button or tilt the phone sideways to trigger full screen - Firefox crashes and forces back to home screen - if opening Firefox again only half of the video component shows as in portrait mode, rest is black screen - if attempting to go side/full screen does properly show the video, but going back again to normal screen still shows the half black screen

I can reproduce this with a almost 100% rate, it only fixes itself by restarting Firefox, where it will work until phone is put to sleep mode.

I tried reinstalling Firefox from scratch, as well as deleting my browser cache and it didn't fix.

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

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)

Sometimes when I click full-screen on a video, the app view disappears, and I am back out on the home screen. I still hear the video, and can switch back to Firefox and try full-screen again. It usually (maybe always) works the second time.

When it happens, I can briefly see the video go full-screen and rotate to landscape. When the view has disappeared the screen rotates back to portrait. Whenever a video stays in portrait mode when going full-screen, the problem does not occur.

Even when closing firefox, I can still hear the video. So I think it is related to this issue: [https://support.mozilla.org/en-US/que.../1420245]

What I have tried:

• Switching versions of firefox, they all have the same issue; Firefox, Firefox Nightly, and Fennec.

• Clearing cache and disabling add-ons has not worked, but seemed to make it happen less frequently for a while (not sure).

• I tried activating automatic screen rotation, but this made the problem worse. It would then not work the second time and firefox would only display part of the website in the top right corner of the screen. Closing it and re-opening it multiple times did not work. I had to turn auto-rotate back off.

• I'm using the KISS launcher. Tried switching to various other launchers, but it made no difference.

OS: Calyx OS 4.12 HW: FairPhone 4 Firefox: Fennec v116, Firefox Nightly Add-ons: uBlock Origin, Tampermonkey

Whenever i have tried downloading anything from firefox, it crashes the system and the boot logo appears. These crashes also take a lot of time to recover from. My phone is vivo s1 pro and its running android 12.

About a week ago my phone (Sony Xperia ZX2 Premium running Android 10) started 'crashing to the lock screen' whenever a download finished in the mobile version of Firefox. If multiple files are downloaded in short succession a popup will appear informing me that the 'System UI keeps stopping', with a prompt to close the app or to get to the app info (see the attached photo - clicking either option sends me back to the lockscreen, with the only difference being that after unlocking the phone the former will have stayed with Firefox in focus, and the latter having opened the Settings app on the System UI entry).

Going to about:crashes shows no recent crashes on Firefox's ends. (Plus, Firefox shows no signs of having been closed [like tabs being reloaded] after unlocking the phone again post-crash). The issue currently only happens when downloading a file through Firefox; downloading a file through Edge, Discord, or the Google Drive app produces no problems.

I have already tried force-stopping and restarting Firefox, restarting the phone, and clearing the download history with no luck. Furthermore, I have also checked for updates for the system, the Google Play Store, and Firefox for Android, however all of them were already up to date.

Any help would be sincerely appreciated.

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 the past few weeks builds, downloading image from any website is weirdly triggering a crash of com.android.phone due to which mobile network is lost as well. Using Samsung Galaxy Note9.

When I want to watch a video on fullscreen on my Samsung tablet, Firefox minimalizes throws me to my homescreen. After I go back to Firefox, the video is choppy and has a low fps. I fix it by forward and rewind the video by clicking on the side of the screen. Very annoying. Browser is up to date, please help

When using Firefox on Android for a while, attempting to use pinch to zoom on a web site will cause Android to crash, as in the screen will go black, the G logo animation will appear, and I'll be sent back to the lock screen. It's not just the app that crashes. It doesn't seem to be a full reboot as that takes longer and starts with a different animation, but some part of Android is restarting.

It's consistent but not predictable. Pinch to zoom will work on one site fine and then crash on the same site later. It seems to be a resource issue as it's unlikely to happen on a fresh instance and it becomes more likely the longer you've been using Firefox.

This has been happening for several months, since at least July. It's happened both on my old Pixel 6 Pro and my new Pixel 9 Pro. It's happened on both Android 14 and 15.

I eventually found out I could go to Settings > About Firefox > Crashes and get some debugging info, but I don't know what to do with it. I currently have 15 crashes between now and Oct 16th which all say:

java.lang.RuntimeException: Adding window failed

Clicking Share to get more info on the latest one adds:

java.lang.RunetimeException: Adding window failed

at android.view.ViewRootImpl.setView(ViewRootImpl.java:1618)
at android.view.WindowManager.Global.addView(WindowManagerGlobal.java:442)
at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:158)
at android.app.Dialog.show(Dialog.java:352)
[...]

Caused by: android.os.DeadObjectException

at android.os.BinderProxy.transactNative(NativeMethod)
at android.os.BinderProxy.transact(BinderProxy.java:568)
at android.view.IWindowSession$Stub$Proxy.addToDisplayAsUser(IWindowSession.java:1305)
at android.view.ViewRootImpl.setView(ViewRootImpl.java:1596)
... 18 more

I don't know what to do with this info. Should I file a Bugzilla report with just this? The GUID associated with the most recent one is 7a5e5497-bb62-4e3c-94fc-5c63c51d0830. I can't look it up in crash-stats.mozilla.org. Or should I assume all crash reports are automatically received? I'd still like to be able to have a Bugzilla bug to watch for progress.

Hello!

Firefox for Android consistently closes whenever I try to play a video in full screen mode.

The steps to replicate this bug are as follows: I go to a website that has a video (like YouTube), I start playing a video, and then I click on the full screen button. Firefox then closes out to the main menu of the home. When I try to reenter the app, the Firefox app becomes a black screen with a horribly offset tiny corner showing a portion of the webpage.

I cannot find any crash reports in the "about Firefox" subsection of the settings

I am using The latest version of Android 13 And my version of Firefox is 114.2.0 (Build #2015957435). I have tried clearing the app cache, and reinstalling the app. Neither fixes it.

Please let me know if I can provide anything further!

Does anyone have any recommended fixes?

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.

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?

Recently I migrated to Firefox to get rid of the unbearable heavy load of ads on Chrome and would be satisfied with such change if it was not by the slow way Firefox handles Youtube player. As I touch to maximize the screen it is a painful process : the image rotates to a smaller rectangle and after some seconds finally fills up the screen. Once in full screen video player control no longer works. The same did not occur with Chrome , in full screen I used to have control. I noticed previously on my desktop running Windows 10 that Fireworks it is much slower to go full screen on Youtube and to exit full screen. I think Firefox handles with more difficulty the Youtube player than Chrome , or perhaps I am missing something. Unfortunately I think I will have to return to Chrome on Android.

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.