Vivaldi noticeably sluggish since upgrading to 3.0

  • This post is deleted!

  • Moderator

    This post is deleted!

  • Having the exact same problem here. Was bringing my monster machine to it's knees (Ryzen 3900X, 32GB RAM, Radeon 5700). Disabling the accessibility flags seemed to have fixed it. I especially noticed it when I was trying to select different product variations via dropdowns on Amazon (for example, on this product: - but it's been doing it on a lot of sites. The entire browser will freeze on each monitor for 20-30 seconds making it unusable for work. Went through and disabled all extensions and it was doing the same thing.

  • Moderator

    @SpaceshipCreative Was the accessibility flag turned on for you without you ever specifically enabling it or did you enable it in the past?

  • @mtaki14 it was turned on for me (by default?) without me specifically enabling it. I uninstalled all extensions besides LastPass and uBlock Origin. I even tested with those disabled.

  • Moderator

    @SpaceshipCreative Interesting. It's off by default on all of my versions, all of my installs. I wonder if some extension(s) might turn it on.

  • @Ayespy could be. It's been driving me insane for a few weeks now. I finally snapped and came here looking for a solution - good ol forums to save the day.

  • some extension(s) might turn it on.

    @Ayespy That would be a chromium bug -- or a very bad design.
    Even on android, when an app need the accessibility services, the user have to agree to enable that.

  • This post is deleted!

  • I'm dealing with sluggishness as well, starting with the 3.x versions. In my case, it looks like a memory leak. I have about 100 tabs open, spread over about 12 windows. After starting Vivaldi with that many tabs, it consumes about 2.3GB of RAM. After leaving the tabs untouched for about 12 hours overnight, the memory consumption is up to about 11GB and after another 12 hours it was at 16GB. Eventually Vivaldi freezes and I have to kill and restart it.

    I haven't changed and extensions or setting recently. See my signature for my configuration.

  • @rhk
    Hi, it leak on both systems? If yes it is a ugly bug.
    Did you check wich process/tab is leaking with Shift+Esc Vivaldi task manager?
    Iirc I had a webpage in a tab that leaks memory, other need 100% CPU and this were not a Vivaldi bug.

    Cheers, mib

  • @mib2berlin Hi Mib

    To answer your questions:

    a) I'm running Vivaldi on about 20 different PC's and laptops. The 2 listed in my signature are the ones with the heaviest use and yes, both are sluggish. Other installs are not as affected, I think it's because they usually have a lot less tabs open.

    b) By the way my history is only kept for 7 days and I have about 2,500 synced bookmarks.

    c) Yes, I use SHIFT+ESC frequently to check on the memory use. The individual windows are between 30k - 200k, depending on the amount and type of tabs. But App:Vivaldi and especially GPU Process are both over 2GB and constantly increasing without any changes in tabs or additional browsing.

    d) I noticed that since the last few updates, especially pages with heavy video or gif content such as news pages are extremely sluggish and sometimes freeze. This despite the fact that uBlock or the new Vivaldi blocker is active. The same pages are a lot spiffier in Edge Chromium Beta.

  • @rhk
    Thanks, I would report it to the bug tracker.
    Even your Vivaldi usage is not common a software should never leak memory, I call this a bug.

    Cheers, mib

  • @aldaviva said in Vivaldi noticeably sluggish since upgrading to 3.0:

    I determined that the problem was enabling Native Accessibility API Support and Web Accessibility in vivaldi://accessibility. When I disable Web Accessibility and Native Accessibility API Support, the performance problem is resolved. As mentioned previously in this thread, it did not reproduce in the last stable 2.x version of Vivaldi.

    I was using those accessibility settings because KeePass2's WebAutoType plugin uses MSAA (IAccessible) to detect the URL of the foreground browser window. I was launching Vivaldi using a small program that always added --force-renderer-accessibility to the arguments list to always enable MSAA in Vivaldi and allow this plugin to work correctly.

    Desperate, I was reading through this thread again when I came upon the above, which I already checked at the time (I even said so above). Imagine my surprise when today I found it looking like this:


    Needless to say, I'll be disabling that and re-testing, but what else can enable this feature (I don't use KeePass)?

    Help/About doesn't show anything about this in the automatic command line, and I started Vivaldi in its normal way. Maybe running with this would ensure it can't be sneakily re-enabled?


    Update: Yes, definitely run with that switch for the foreseeable future. It prevents the issue.

  • Moderator

    @rseiler I don't know, but my rough working theory is that some extension turns it on.

  • @rseiler said in Vivaldi noticeably sluggish since upgrading to 3.0:
    Maybe running with this would ensure it can't be sneakily re-enabled?


    That's what finally got my issues to stop. I wish I would have known about it before reinstalling Windows (freezing kept occurring afterwards). One good thing that came from the reinstall of Win 10 was getting my SSD and regular HD setup to work together better.

  • Considering Keepass, I have to wonder if Lastpass, one that I do use, would be a top suspect.

    The problem seems dependent on something else, too: certain sites, or perhaps certain usage of the extension. Maybe when you hit the right combination of extension and page, Accessibility is triggered, and from that point forward you're susceptible to the problem. There definitely seemed to be a threshold like that for me, but unfortunately I only visited the Accessibility page once before today, and it was before the problem triggered that day, so I eliminated it as a possibility.

    BTW, is this fix in today's build about this issue or some other one?

    [Regression] Slow page load performance (VB-67537)

  • Moderator

    @rseiler said in Vivaldi noticeably sluggish since upgrading to 3.0:

    BTW, is this fix in today's build about this issue or some other one?
    [Regression] Slow page load performance (VB-67537)

    A internal optimization where some URLs loading slower than on Chrome.

  • @rseiler @Ayespy Some Ease of Access settings in Windows can turn it on. For example I found that if I enable the text cursor indicator (Windows Settings->Ease of Access->Text->Turn on text cursor indicator) and then restart Vivaldi, the accessibility modes are automatically enabled in vivaldi://accessibility When I disabled text cursor indicator and restarted Vivaldi, the accessibility modes were disabled again.

  • Moderator

    @emanx995 Fascinating.

Log in to reply

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.