Форум спільноти Firefox для Android

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.

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!

Frequently crashes without warning, pages lag constantly where scrolling down is impossible, even after the page is refreshed. Creates way too many new tabs (like 50 a day) and ads mess up the design of the webpage.

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]

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)