Opera lock up randomly every 5 to 10 seconds (66.0.3515.27)
-
thomas-rager last edited by
@robomike
I tried to disable hardware acceleration. I did this in VirtualBox and also tried the Opera setting. Did not fix my problem.
I think the problem is related to this sandbox issue... -
A Former User last edited by
@thomas-rager : no, the problem returned for me after disabling hardware acceleration in VB. But the permanent crashes of the whole VM stopped.
Well - a new strange observation, is anyone able to confirm?
When I open the "Taskmanager" (Opera menu, developer Tools, key shortcut "shift-escape") and let it run, even in the background, then the lags and locks seem to be significantly shorter. But only as long as the "Memory Usage"-Tab is activated... seriously?
-
Northnet last edited by
@robomike Weird, but true! The lock-ups still occur, but less frequently, and probably shorter too. I wonder if any of the Opera techies are reading this thread, or are we wasting our time?
-
soundchaser59 last edited by
@Northnet
Not helpful for me yet, as I'm using LM 19.3 Tricia and my desktop is Mate 1.22.2 and
base is Ubuntu 18.04 bionic. When I click on the button to check for Opera updates it tells me my version 66.0.3515.103 is already up to date.Maybe I have to uninstall and download again and see if I get a newer version.
-
soundchaser59 last edited by soundchaser59
Well, now I am very hopeful! I followed @Northnet 's lead and manually downloaded and installed the latest version 67.0.3575.31 (after doing a complete removal using synaptic package manager).
I have been surfing and browsing now for almost an hour with no freezing and no lockups!
It was interesting that I had to manually download the latest package from the Opera web site and use gdebi package installer to install it before Opera recognized it as an update. When I tried to use Software Manager it told me there were missing dependencies and packages required that would not be installed, etc. So I closed that and played a hunch by using the gdebi package installer, and it seems to have worked fine. It even said all dependencies were satisfied.
So far so good!
THANK YOU Opera devs for attention to this issue! Time to import bookmarks!
-
pindos last edited by
I have small freezes yet after update to Opera 67. This happens on some page with heavy content.
-
Northnet last edited by
Some time after the update to 67, I can confirm that my issues are completely resolved. This is my low power (Pentium - 4Gb RAM) browsing laptop, and not only is it not freezing, but responsiveness is distinctly better. Better than Firefox on the same machine, and feeling positively 'snappy'.
@pindos If page content is causing a problem, I think maybe it is time to consider your local resources. Lagging processor, insufficient memory, cache waiting for disk to catch up, that sort of thing?
-
zibi1981 last edited by
Opera still freezes on my system if not started with "--disable-seccomp-filter-sandbox" option. But when I want to add some more security to it using Firejail and AppArmor, Opera is not saving any settings! Every start gives me a welcome window and I have to reconfigure it again. I don't have the time and patience and I've switched to Vivaldi for now. It works perfectly with
firejail --apparmor /usr/bin/vivaldi-stable --disable-seccomp-filter-sandbox %U
-
thomas-rager last edited by
With the newest Opera version the freezes are gone in the VM. Sadly is this version constantly freezing/crashing on my Thinkpad with Linux Mint 19.3. I don't know if the Devs at Opera are testing their Linux build proper. But this is really annoying. In the VM I will use the latest Version and on my Thinkpad I will stay with 66.0.3515.72 and the ffmpeg fix.
-
minho last edited by
@thomas-rager if synchronization is enabled on your linux mint, disable it.
Then freezing will probably stop. -
thomas-rager last edited by
@minho I currently stay with version 66. This version is usable. I don't have time to beta test every new Opera Version.
-
A Former User last edited by
Just to update, some months ago, Opera managed to fix this, and thank you all the programmers for this fix.