Firefox tabs keep crashing
Hello, I've been having issues with the Firefox app on my Android ever since the most recent update on 4th of July. Whenever I tap the "tabs" button, the tabs viewer opens as always, but if I try to scroll and browse the tab, or if I try to close any of the visible tabs, the whole app crashes. Because of that, I can only switch between tabs by swiping, but it can be annoying if you're used to using many tabs like myself. I have cleared my cache multiple times and it didn't help. I am not too tech-savvy but is there any way to fix it? Thank you!
선택된 해결법
Update: The problem has been solved after I updated the app with the 15th of July update!
문맥에 따라 이 답변을 읽어주세요 👍 0모든 댓글 (3)
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.
I have tried closing the apps and clearing cache multiple times but neither help.
Here is the Socorro link you requested, I hope this is what you meant: https://crash-stats.mozilla.org/repor.../d0873e06-9fa7-45fc-9e00-843890240720
선택된 해결법
Update: The problem has been solved after I updated the app with the 15th of July update!