Firefox crashes Android system and System UI processes after every image download
Firefox crashes Android system and System UI processes after every image download.
It happens after every image download finishes.
Firefox version in screenshots.
Izabrano rješenje
Hi
This is something that our developers are looking into and hope to have resolved very soon. You can follow progress on this at:
https://bugzilla.mozilla.org/show_bug.cgi?id=1847141
Pročitaj ovaj odgovor u kontekstu 👍 2Svi odgovori (7)
Android 10 on Sony XZ2 Compact.
Hi
That Android error message seems to state that it is the Phone app that has crashed, not Firefox for Android. I recommend that you check for updates from the Google Play store for the Phone app.
Hi, you are right, it's the Phone app and Android System UI that crashes. It happens *every* time I download an image (I checked different images before submitting) and I haven't experienced it before or experience it doing anything else on my phone.
I've tried Force stopping the Phone app and opening it again to see if that does anything, but I have a hard time seeing how it could have anything to do with that? I haven't ever had the Phone app crash before.
I thought it was a part of Android system since the display goes black for a couple seconds and then the lock-screen appears after that, but that must be because of System UI crashing.
Odabrano rješenje
Hi
This is something that our developers are looking into and hope to have resolved very soon. You can follow progress on this at:
Same issue here, but no matter what type of file is downloaded. Happened to me with ZIP, DOCX, PDF, image files. Tried to uninstall, then install again Firefox without addons and setting up synchronization. Didn't work. The phone as a whole crashes to loading screen, then after a second or two (faster than reboot) lockscreen appears like after turning the phone on.
HTC Desire 21 Pro 5G (Android 10). Firefox ver. 119.0 (Build #2015980915), 367d60e851+ GV: 119.0-20231019122658 AS: 119.0
This issue was resolved for me in update 118. Please make a new post for 119 if you're still experiencing this problem. :)