Opera app isnt starting anymore since 6.1
-
bamhamer last edited by
Am I the only one that can't use opera on the iPhone anymore since the 6.1. update?
I get a loading screen and a notification that my tabs are getting migrated, and after a while it just shuts down.
6.1.2 didn't solve the problem, unfortunately. -
MariChrysanthemum last edited byI have not been having this problem. Maybe it has to do with device software? I'm on iOS 18.7 right now. Gonna check 26 later.
-
bamhamer last edited by
@MariChrysanthemum problem occurred on 18.7 and on 26. it's very frustrating because if it's not getting solved I've lost all my open tabs and bookmarks and I have to use another browser now...
-
bamhamer last edited by
Seems like I'm the only one with this problem, which possibly means there's little hope this will get fixed...
-
jonaballen last edited byHi
We are sorry for the inconvenience.
A small number of users that upgraded to 6.1.0 and 6.1.1 have reported the same issue. Startup freeze/crash with blank screen and spinner appearing.
There is a fix in the latest version 6.1.2. Have you tried to update?
The issue is triggered by a database upgrade and occurs during the data migration process. If you have a very large database (after long use of the browser) it can consume too much memory, so the system kills it.
We tested the process extensively before 6.1.0 release, but unluckily, we did not manage to reproduce and identify the issue until after users reported the problem.
The 6.1.2 update/fix will minimise memory usage and add several guardrails to avoid the issue. However, the process will take longer time because we need to split it up to avoid memory over consumption. So the longer history and the more tabs you had, the longer it takes. In the extreme cases, it could be up to a minute.
Kind regards,
Opera Team -
jonaballen last edited by
P.S.
At least one case seems to still hit the "memory wall" even after the 6.1.2 fix and we have another fix in the next update .That will lower memory use to the absolute minimum, but also prolong the migration process even further. The browser will attempt to upgrade normally first and if it fails and get killed, the next start will detect the failed attempt and try upgrade with minimal memory use resulting in a slower but safer process.
-
tripleshieldedgaming last edited by
@jonaballen This has not been fixed! My app fails to work and keeps closing itself after 10 seconds of "Migrating Tabs". I have 9000 tabs and I need them for my job!
-
jonaballen last edited by
@tripleshieldedgaming
Then you should wait for next update, in which we will have a fallback.@jonaballen said in Opera app isnt starting anymore since 6.1:
P.S.
At least one case seems to still hit the "memory wall" even after the 6.1.2 fix and we have another fix in the next update .That will lower memory use to the absolute minimum, but also prolong the migration process even further. The browser will attempt to upgrade normally first and if it fails and get killed, the next start will detect the failed attempt and try upgrade with minimal memory use resulting in a slower but safer process.
-
bamhamer last edited by
@jonaballen thanks for the reply. 6.1.2 didn't solve the issue. After around 20sec the app closes and after that the phone is almost unusable because of the lag for several minutes.
I had indeed several hundred tabs open at the time of the update and I hope there can be a fix of this situation without reinstalling the app
