Persistent crashes when pinching to zoom on Firefox Android
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… (čitajće wjace)
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.