Opera horribly lagging and constantly freezing after new Graphicscard.
-
burnout426 Volunteer last edited by
Maybe reset all the flags in
chrome://flags. Maybe enablechrome://flags/#ignore-gpu-blacklistif needed. -
burnout426 Volunteer last edited by burnout426
For testing you could try launching Opera's launcher.exe with --disable-gpu (which I think does more disabling of the GPU than the option in settings, but I forget). See https://peter.sh/experiments/chromium-command-line-switches/#disable-gpu.
-
A Former User last edited by
I'm a long time Opera user, and I've started to experience this issue since the last update (57.0.3098.76 on Win10 64bit).
I have an Nvidia 1050 Ti and as @burnout426 suggested, I started Opera with --disable-gpu. I can confirm that the situation did not improve at all.
I'm noticing the lag on page loads (freezes for almost a second) and occasionally on tab switching. Never before have I experienced these lags. On my work PC, I'm not experiencing the same issues.
I've gone as far as disabling all the extensions, and re-installing Opera. No change at all. I do not experience any lags on the latest Chrome for what it's worth.
-
franken5 last edited by
I have the same problem for a 4-5 days after last two updates.
OS: Win10 Pro 32bit
CPU; Core 2 Duo 5600
GPU: GF 550Ti -
burnout426 Volunteer last edited by
@pingu01 Download the Opera Developer Win x64 offline installer linked on the right-side of https://blogs.opera.com/desktop/, launch it, click "options", set "install path" to a folder on your desktop, set "install for" to "standalone installation", and install. Do things at least work fine there.
@franken5 Do the same but with the non-x64 offline installer since you're using 32-bit Windows.
-
A Former User last edited by A Former User
@burnout426
After few minutes of testing I can say that the standalone Developer version is working fine...it is maybe a bit slower than what I was used to before the lagging problems started (it is slower than Chrome and before the problems I think the speed was comparable, maybe little bit better for opera). But that might be just a feeling. It is definetely not lagging nor freezing.
Testing it on i3-540 with integrated GPU, will test on nvidia GTX1050ti later. -
A Former User last edited by
I dont think that this problem really is hardware related.
Many people experience the same issues i do with an i7 and an rtx 2070.
Some have Windows 10, some, like me, Windows 7 (64bit).
I guess its after a new update, but still it laggs my whole PC when i open Opera.
This is a huge problem, because i am used to Opera and i dont want this crap Google-Chrome.
I hope, a solution is coming soon. Maybe re-install, but i dont want all my settings and tabs to be deleted. -
burnout426 Volunteer last edited by
@vsaniter said in Opera horribly lagging and constantly freezing after new Graphicscard.:
After few minutes of testing I can say that the standalone Developer version is working fine
Okay. Can you test a standalone version of Opera Stable just to be certain you can reproduce it in a clean profile without any extensions and without Opera Sync enabled.
-
burnout426 Volunteer last edited by
Anyone try with all extensions disabled to see if it makes a difference? Anyone using Opera Sync? If so, can you disable it for a bit to see if there's any difference?
-
burnout426 Volunteer last edited by
@spacelarry said in Opera horribly lagging and constantly freezing after new Graphicscard.:
Maybe re-install, but i dont want all my settings and tabs to be deleted.
Can you try with a standalone installation of Opera Stable just to test with?
-
A Former User last edited by
@burnout426 Installed Opera dev edition on the desktop as suggested, and I had no lag at all.
I went back to the normal installation with all extensions disabled, and also experienced no lag. So I started enabling extensions one by one, and the lag starts when I enable a particular extension called Wappalyzer (installed through the Chrome store). To confirm, I disabled it and enabled it several times, and each time after enabling it the lag comes back. By lag, I mean freezing on page loads (sometimes several seconds) and occasionally when switching tabs.
On the previous version of Opera, this extension does not cause any issues.
-
burnout426 Volunteer last edited by
@pingu01 said in Opera horribly lagging and constantly freezing after new Graphicscard.:
Wappalyzer
Anyone else using this extension?
-
burnout426 Volunteer last edited by
@pingu01 said in Opera horribly lagging and constantly freezing after new Graphicscard.:
On the previous version of Opera, this extension does not cause any issues.
Enable the extension, goto
opera://extensionsand check "enable on search results", does the extension start behaving? -
franken5 last edited by
You know, I turned off all my extensions and freezes are gone. It seems that some Aliexpress extensions works bad with last update. No lags and freezes yet.
-
burnout426 Volunteer last edited by
Awesome. With your help, Opera was able to figure out what's wrong and fix it. It's a simple fix (not a new version, but if there's a new version available, update) that you should get through auto-update. You just need to restart Opera for it to be applied.
Can you try to restart Opera and try again. Maybe do a check for updates just for good measure and then restart?
-
-
A Former User last edited by A Former User
Yeah it might have been the AliTools extension. But it got updated and now it works fine again.
-
A Former User last edited by
I can confirm it's working normally with the Wappalyzer plugin.
@burnout426 could you disclose what the issue was? I'm sure the Aliexpress and Wappalyzer extensions have some similar behaviour for both to be affected.
-
burnout426 Volunteer last edited by burnout426
@pingu01 said in Opera horribly lagging and constantly freezing after new Graphicscard.:
@burnout426 could you disclose what the issue was?
Sorry, I don't know any details except that it was an issue with a setting (not sure if that was meant as a simple preference issue or if it meant a setting with one of Opera's internal extensions).
I would guess that it had something to do with the extension blocking on search pages feature though.
