We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Læs mere

Persistent crashes when pinching to zoom on Firefox Android

more options

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.

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.

Alle svar (4)

more options

Hi

I am sorry to hear that Firefox for Android is crashing. I hope that we can help resolve this for you. Before following the steps below, make sure that you have updated both your Android device and Firefox for Android to the latest versions available.

As a first step, close down many of the tabs that you have open to as few as possible. Does this help reduce the incidence of a crash?

If this does not resolve the issue, open the Android Settings app, select Apps then find Firefox in the list. In the section titled Storage and Cache, select the option to clear the cache (do not clear data!). Does this help?

Following that, our developers will need to look into this in more detail with some logs from inside your copy of Firefox for Android. Type about:crashes in the address bar which will display information about recent crashes. If you select the most recent Socorro link, a crash report will open in a new tab. If you could copy and paste the address of the page that opens into a reply to this thread, we will be able to look into this further for you.

I hope that this helps.

Nyttig?

more options

I've tried clearing the cache through Android before. I'm using the latest version.

In about:crashes there are 16 entries "java.lang.RuntimeException: Adding window failed" from 10/16 to 11/30, none of which have Socorro links, only Share links. After that there's 11 "<native crash>" entries, all supposedly from the same time 9/30, only two of which have Socorro links. Those two links are below:

https://crash-stats.mozilla.org/report/index/ddf542ba-42fa-43b8-a15d-242ea0240930 https://crash-stats.mozilla.org/report/index/c65a7551-50eb-4d8e-ac24-99bf20240930

Nyttig?

more options

I realized Settings > Data Collection > Automatically Submit Crash Reports wasn't turned on, so I turned that on. Another "Adding window failed" crash has happened since then but about:crashes still doesn't show a Socorro link for it, only Share. Searching crash-stats.mozilla.org for the GUID above it (fd620cd7-3177-4b85-bd0d-d5e03f81c538) doesn't return anything.

Nyttig?

more options

Nope, turning on Automatically Submit Crash Reports doesn't result in Socorro links on the crashes that have happened since then.

Nyttig?

Stil et spørgsmål

Du skal logge ind på din konto for at svare på et indlæg. Start et nyt spørgsmål, hvis du ikke har en konto endnu.