freeze on android 13
initially wrote this in the Google reviews and got told to put this here, I will copy my text:
```of course the only browser currently usable mobile or otherwise. I am mostly here to report an issue, fairphone 4 / android 13 app freezes on tapping search bar
steps to reproduce : open browser and use normally for some time click search bar
this is not a brilliant diagnosis I know but it seems to be a memory issue and I don't have the toolkit to properly check. large amount of tabs open and long media consumption and fast opening and closing of tabs all seem to impact the speed of this occurring so this made the most sense to me
restarting usually fixes the issue but deletes the last ~2min of activity. very strange all in all, I will again suggest a memory leak as the problem```
Όλες οι απαντήσεις (2)
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 Applications then find Firefox in the list. In the section headed "Storage", selct the option to clear the cache (do not clear data!). Does this help?
Failing 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'm sorry to say this so bluntly haha but of course clearing cache will solve this temporarily without actually getting to the root of the problem
and if the memory leak causes a user session to supercede the allowed space of the application, then also it won't file crash reports (which is exactly what I'm experiencing)
I have no recorded crashes in about:crashes even though the app crashed thrice while I was visiting the link. clearing cache puts me into the position of being able to write this, but it doesn't absolve the devs of the responsibility of fixing this haha this is a breaking issue
Πρέπει να συνδεθείτε στον λογαριασμό σας για να απαντήσετε σε δημοσιεύσεις. Ξεκινήστε μια νέα ερώτηση εάν δεν διαθέτετε ακόμα λογαριασμό.