Форум поддержки Firefox для Android

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.

On youtube mobile site or a reddit video, when I click the bottom right button to fullscreen the video, a message pops up that says 'entering fullscreen mode' (with a firefox logo on the left of the message) and then firefox closes and I'm at my android home page

This seems to happen when I watch videos in a new instance. If I reopen firefox to the video and then try fullscreen again, it goes full screen no problem. So basically it's annoying and happens when I try to watch any video full screen for the first time.

Is this a known bug? Wasn't an issue on my old phone (I just got the galaxy s23).

Firefox is fully updated from playstore. Only addons installed is ublock origin and Privacy Badger

Thank you for any assistance

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)

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)

while performing a download, "com.android.phone has stopped" apears, the signal strenght indicator in the upper right restarts(disappears, reappears with the 4G mark, the mark disappears and the indicator works after), after that the phone service and the phone app work normally. the download finishes normally.

using motorola e7 plus, android 10

tried restarting the phone, deleting cash and data of phone app, deleting cash of firefox

tried downloading using google chrome, all work normally.

it is possible that the issue started happening after I updated firefox but It's possible that it was happening before too.

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?

Going to full screen on YouTube (and other video websites) usually breaks the Firefox app on pixel 7 pro. It keeps playing but just closes and can't be reopened. I have to stop the app, open it again, and try again. Does anyone know how to fix this?

Not exactly sure what update started this but it worked fine before. I use Firefox on s23 ultra and tab S8 ultra. Both are signed into and I've tried to reinstall the app but still doesn't fix the problem. If I go on YouTube or a website that has video, if I click on full screen the app closes down but keeps playing the video. If I open the app and hit full screen again it then works and fills the screen with the video. If I could go back to a month ago maybe since this is pretty new bug. I do have add-ons but even with a clean install and no add-ons it still does the same thing. Was referred here from the play store.

My pixel 5 still has the bug that Mozilla claims they fixed where if you rotate the screen of a video to landscape then it will send the app to the background or will not fully rotate and more the half the screen will be cut off. Will this ever be addressed? It's been months now.

The only 'fix' seems clicking on the app and sending it to the background over and over.

I am posting this issue at the request of E from Firefox's app developer feedback after I submitted an app review.

The app continues to be unstable on my Pixel 6a (latest OS, Android 13) after freezing up on what appears to be any heavily scrolled pages or those that create a heavy cache. This freezing then causes abrupt phone restarts shortly thereafter, but not always immediately. Usually the culprit seems to be linked to Facebook album viewing, Imgur albums with article-length descriptions, etc. The abrupt phone restarting occurs whether force stopping Firefox and clearing the cache right away or not (although the restarts seem to happen faster if I force stop the app). I have simply closed the app during the freeze, put my phone down, and come back minutes or hours later to it having restarted on its own.

In addition, open tabs have a tendency to lose their scroll spots on a non-infinitely-scrolling page (e.g. an article not requiring expanding) when the app is minimized but not closed. This is probably unrelated(?) and isn't as critical as the spontaneous restarts, however.

It looks like many Pixel 6a users have had this issue, although those support threads from 8-9 months ago have now been archived. Someone else mentioned scripts from the websites themselves may be to blame? Would be curious to hear of any specific fixes. Thanks!

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.

Dear Concern, Suddenly I Found Crashing Problem In Fire Fox New Updated Version. When I Try to Save Any Image Or Download Any File From it’s show A Crashing Problem. I attached A Photo Of This Crashing Problem. Sir Please Fix The Problem As Soon As Possible. Thank You.

All video players on websites will, if viewed in full screen, close the firefox app on my android device. The app gets minimized and can be opened back, but all pages become bugged then and appear in half the page only, links cannot be copied either, the page will only work partially when my phone is held horizontally. This issue happens with or without auto-rotate enabled. The bug most often happens as soon as I set a video on full-screen, but can happen while the video is playing also. I tried disabling all of my add-ons and the bug still persists(I will attach a photo of my addon list). Here is a video of the bug after the app closed and I reopened it.

https://youtube.com/shorts/8dlWJHTrsOA?feature=share

as the title says when downloading a file, firefox causes com.android.phone to crash. enough crashes causes my tablet to panic and auto restart itself.

the only app that can cause this is is firefox, downloading files via something like discord, doesn't trigger it, only firefox. i tried with other apps to no avail.

it started happening after an update (update TB-X606F_S301018_230810_BMP ) (the last update was a year ago so lenovo isn't gonna fix it on their end anytime soon) and it's quite annoying when i need to use firefox to download files to view/use.

Details:

 Device: Lenovo Tab M10 FHD Plus (TB-X606F)
 Android Version: 10
 Firefox version: 117.1.0
 security update: 2023 Aug
 Google play system update: 2023 May
 Lenovo system version: TB-X606F_S301018_230810_BMP

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.

I have an quite annoying issue when I'm streaming something from SVT Play (www.svtplay.se).

The issue is that when I'm trying to stream anything from this site; I've noticed that the resolution is quite messed up. Insted of having an "normal" resolution ( in wich I have all the basic settings such as full screen,Text ON/ OFF etc), the resolution get a bit odd. In the beginning it's just an small screen ( aprox of an 6x6 cm), but when I'm entering Full Screen; the resolution is all over the place+ that the menu bar is missing.

But also that if I'm entering Full Screen mode; the app is " crashing", or should I say minimizing itself and that I go back to my home screen. But stangly the cast isn't interupting. When I'm trying to enterkng the app,the web- adress is missing( not physicaly but just empty).

What's more strange ( or should I say annoying), is the fact that the cast hasn't any stable resolution. Instead of having an normal resolution( cast), it's rather of an 1,5. But strangly the voice is normal. It's only the picture in wich is out of sync. But strangly if I choose the option of limited bandwith it goes back to normal.

But what's more strange is that I have full connection.

I don't know how this came,but since I'm downloading it from Play store. However since the best way is to download an APK- File( in wich my device is compatibel with). Since I have an Samsung Galaxy Tab S9FE ( SM-X516B- series)

Because however on older version it wasn't any problem. It just appear in newer versions.

However when I'm shutting down the app( have activated the option of clear history when close), it sometimes work fine. But in worse scenario I have to reinstall the app.

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.

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