Vivaldi noticeably sluggish since upgrading to 3.0
-
@Darthagnon said in Vivaldi noticeably sluggish since upgrading to 3.0:
--disable-renderer-accessibility
Love using that switch, as it completely solves the problem. I don't see not using it in the future just as a safeguard, but I'm curious, is anyone testing the problem in the 3.1 builds so far?
Just to update this post with some further info:
If you want to cover the case where Vivaldi launches another way, like from a mail app, that can be done in the Registry:
https://i.imgur.com/1LPzBL3.pngSo, you insert the switch into the place shown. And note that your exact location in the Registry will differ, since Vivaldi uses a random sequence of characters after the VivaldiHTM.
BTW, it's possible that one or both of these flags would eliminate the need of the switch entirely, but the descriptions for them aren't overly clear, so they may or may not serve our purpose:
chrome://flags/#webui-a11y-enhancements
chrome://flags/#enable-accessibility-expose-display-none -
I was rereading my older posts in this thread which I've now deleted. A mod asked me something and I replied thinking I was responding by saying using --disable-renderer-accessibility at startup worked. I mistakenly said something else. Just to clarify for my own sanity so this will quit bothering me adding "--disable-renderer-accessibility" at startup is what solved my issues with Vivaldi freezing along with the onscreen keyboard doing the same.
-
Took me a while, but I sent an email into the void, as a reply/update to the Vivaldi bug report.
-
@Darthagnon said in Vivaldi noticeably sluggish since upgrading to 3.0:
Took me a while, but I sent an email into the void, as a reply/update to the Vivaldi bug report.
I can confirm that the void has received your message
-
There's a registry entry you can make, as explained by rseiler here:
https://forum.vivaldi.net/topic/47583/stabilization-for-3-1-vivaldi-browser-snapshot-1929-13/32Registry Entry:
Computer\HKEY_CLASSES_ROOT\VivaldiHTM\shell\open\command
Before:
"C:\pf_Speed\Vivaldi_stable\Application\vivaldi.exe" -- "%1"
After:
"C:\pf_Speed\Vivaldi_stable\Application\vivaldi.exe" --disable-renderer-accessibility -- "%1"
This will ensure Vivaldi opens (even from shortcuts/urls/links) with maximum performance and no lag every time (until this awful bug is fixed).
-
Speaking of which, is anyone on 3.1 still seeing the problem? It's in quasi-final state at the moment with the special builds (not to be confused with snapshots) made available to seekers.
-
@rseiler I haven't seen any freezes so far with 3.1, but in comparison to other browsers, Vivaldi still doesn't feel as fluid and fast. I have a powerful machine, but opening a new private Window takes about 2 seconds in Vivaldi. In all other browsers I've tested (Edge, Opera, Firefox), a new private window opens in under one second.
-
@HellbillyDeluxe I don't know what you call a "powerful" machine, but here, a new private window opens in less than a second. In my former "powerful" machine, the one in my signature (which I will be changing today), a new private window takes nearly 8 seconds to build. This is partially down to the fact that Vivaldi builds an entire extra layer, the one housing all of its customization and modification ability, which Edge, Chrome and Firefox do not build, because they make their UI out of elements native to the system, and therefore, they are not able to develop full customization like Vivaldi.
(signature concerning my old tower - Windows 10 X64, AMD A10 8750 @ 3.6 GHz; ASUS EAH5450 graphics; 1TB Crucial MX500 SSD; 16 GB DDR3 PC3 12800 RAM)
-
Some of my PC specs:
AMD Ryzen 5 2600 Six-Core CPU ~ 3.4 GHz
32 GB DDR4 RAM 3200That should me more than enough for Vivaldi to run smoothly, but I understand that Vivaldi's UI is the bottle neck and slows things down. I hope they can improve on that in the future.
-
@HellbillyDeluxe said in Vivaldi noticeably sluggish since upgrading to 3.0:
Some of my PC specs:
AMD Ryzen 5 2600 Six-Core CPU ~ 3.4 GHz
32 GB DDR4 RAM 3200That should me more than enough for Vivaldi to run smoothly, but I understand that Vivaldi's UI is the bottle neck and slows things down. I hope they can improve on that in the future.
I have lesser specs than you but launching a private window takes less than half a second for me. Do you have an SSD?
-
Yes, I have a 512 GB Samsung 860 Evo SSD.
-
Sure, those in the know use the switch, but just for future reference, is this fundamental problem that's been around for several months and which blindsides people fixed in 3.2?
-
@HellbillyDeluxe good grief do people seriously sit there with stopwatches timing browser performance.?
if it were 20-30 seconds which would be noticeable then yea it is an issue but i see this timing nonsense everywhere where if one browser opens a second quicker then they switch like a flock of geese.Nobody will notice a 2-sec delay.
-
@Priest72 Don't confuse that comment, which is about something else, distract from the problem throughout most of the thread, which is about a 20-30 second delay.
Throughout a long thread like this, once in a while people will come in with side issues.
-
There's no need for a stopwatch. When there is a perceived performance issue, the browser offers profiling tools built-in that will measure performance, as well as help diagnose the issue. If people seem to be experiencing performance problems, then the best thing to do would be to profile it.
This is primary way to get an objective measure of performance, and also diagnose performance problems. It can surprise you as well. I can't count the number of times I've seen someone report a perceived performance issue, and point to another product or configuration that supposedly performed better, only to discover the opposite was true after they were profiled.
On the net, I've seen this lead to flaming responses as someone just digs in and defends their their claims, disregarding the evidence, and ending in personal attacks. But in collaborative teams developing software together, it's an invaluable tool.
So if you're experiencing persistent performance problems, especially ones that others are having trouble reproducing, it's likely worth your while to learn how to use the dev tools to measure performance and diagnose issues. If just a few people are having problems while most aren't, then in the absence of other relevant information, I'd venture to guess there's some configuration or extension as the root cause. Which could probably be tracked down using these tools.
Here's a link to Google's getting started guide. There might be a more recent page on the topic, I just grabbed this quickly from a web search. So I'm not vouching for it as the best starter guide, just helping those who may be interested jump start their research.
-
I'll be curious if anyone can reproduce this specific issue (as opposed to other instances of sluggishness) in 3.4
I've been testing RC1 and repeating known problem areas, like certain actions on Amazon, but have not seen the problem repeat.
I'm not currently using the switch workaround.
-
@rseiler , I'm on 3.4 and still experiencing Vivaldi causing explorer to hang...
-
@gcbrown Explorer? I'm not sure how that relates to Vivaldi. Whatever that is, it sounds like something else.
This issue was a very narrow one that caused delays in Vivaldi, not Explorer. Sometimes Vivaldi could even go into a "Not Responding" state in that time. The above-mentioned switch prevented the issue, proving it was related to the Accessibility feature in Chromium.
It does seem resolved in 3.4.