Opera Beta hangs right after starting
-
l11czgawa5 last edited by
Hi all,
I am using Opera Beta for Android v 29.0.1809.92117 from the Play store. My phone is European Samsung Galaxy Note 4 with stock Lollipop 5.0.1.
My problem is that Opera hangs right after starting it.
When I tap on its icon, it starts, opens a new page and I can see the texts on my quick dial icons, but the icons are missing. I cannot interact with Opera in any way and after the timeout, Android prompts me to kill the process.
Screenshot 1, Screenshot 2.I have already cleared the cache from Settings -> Application Manager -> Opera beta -> Clear cache. I do not want to clear program data, because I fear I will loose my 22 opened tabs. I do not sync operas among devices.
What can I do to fix the issue?
To be honest, my top priority is to get the links in some of the opened tabs. If I can get them, I can happily re-install Opera, clear the data, etc.
Let me know if you need more information to resolve the issue!
-
Deleted User last edited by
Check storage-cache size (total) + app memory allocation (app manager), can you see any difference after phone reboot?
-
emoller last edited by
@l11czgawa5 I presume you don't have a rooted device? It's pretty hard to diagnose this when it's happening on startup as we can't get any additional info from our crash reporting tool. Your best chance would be if there happens to be an obvious bug that can be identified from the android logs. Most often that's not the case but we might be lucky.
You'll need to hook your phone up to a computer with a USB cable, enable remote debugging, installing a command line tool called adb (Android Debug Bridge) and getting the logs by typing adb logcat and then starting Opera and paste the log here.
Takes a bit of effort but if you're tech savvy and really want your urls back...
-
l11czgawa5 last edited by
Hi @emoller,
I've got the logcat log, but it contains both personal and work related information. I am not posting it publicly for obvious reasons. Please suggest another way to get it to Opera staff.
Or at least, suggest me which part of it you are interested in and I'll cut the rest. -
emoller last edited by
You could probably narrow it down a lot by going
adb logcat -c
to clear the log, then launch opera and go
adb logcat -d
to dump out what has appeared since you cleared it.
If you don't what to paste the results here, then please file a bug report at https://bugs.opera.com/wizard/mobile?pl=Android and then ping the ANDEX-??? number you'll be told about once you complete.
-
ohrn last edited by
Thanks, using the logcat information I've identified the problem. There is an overflow related to the list of downloaded files.
I hope to get it fixed in Opera 30 but I can't make any promises.
-
frankconline last edited by
Hi, I've got the same issue. I'm using Opera browser for Android. Version 29.0.1809.92697 updated on May 27, 2015. I don't want to lose the current session. Is there any way to recover the url of the opened tabs?
Thank you. -
l11czgawa5 last edited by
I have installed the latest Opera beta release and verified that the bug is fixed. I can use it as usual.
Thank you very much for your help!
-
ohrn last edited by
It's only possible if you have a rooted phone, then you can inspect the file appstate.bin in Opera's profile directory. It's in a binary format but the URLs should be plainly visible among the gibberish.
-
Deleted User last edited by
In Screenshot 1 I've seen that Opera is sized at 103 MO, that's normal for Lollipop 5.0.1? On JB and KK is 62-64 MO after installation, at times could be up to 89MO in size following a pattern related with location request.