Vivaldi uses 100% of one of CPU cores on each update via Software Updater
I noticed a problem with Vivaldi which makes it just a bit uncomfortable to update the browser. Once I update Vivaldi, one of browser processes starts using 100% CPU core's time and my laptop's cooler sky-rockets. I close browser window but the process is still alive. Then I stop the process and run the browser, everything is alright then, CPU usage is fine until next update happens.
That happens on each browser update. See the screenshots attached:
OS: Ubuntu Ubuntu 20.04.2 LTS 64-bit
GNOME Version: 3.36.8
Windowing System: X11
Intel Core i5-10310U CPU @ 1.70GHz × 8
Mesa Intel UHD Graphics (CML GT2)
There's a strange problem with forum - I try to edit first message and an Akismet spam warning pops out.
@shalguev The spam filter is strict for new users. Now you have a couple of reputation points, you should be able to edit your posts.
Welcome to the Community. Here are a few links for your bookmarks that you may find useful:
ugly last edited by
Yes, I've noticed this as well. I'm on the snapshot channel.
I'm not sure when it started. I noticed it at some point during the 3.7 cycle (before the release candidates).
After updating, one core will get stuck at 100%. And will remain there until I manually kill the process. And there are no issues until the next update.
I assume the process gets stuck maxing out a core from when I close the old Vivaldi version after performing an update (as opposed to being caused when first opening the new Vivaldi version), but I haven't tested this out yet. The problem is that I tend to forget about the issue until it happens on the next update.
I'm on Linux Mint 20.1, Cinnamon edition.
[Very long shot] ... Hmmm, so that's a Ubuntu installation, & a Ubuntu-derivative distro, with this strange symptom. It never happened to me in Manjaro, & doesn't happen to me in Arch & Debian. I wonder if there's something unique to Ubuntu that underpins this odd thing?
@guigirl BTW, on my second Ubuntu 20.04 machine nothing similar happens.
UPD: I was wrong, the same behavior on the second machine.
@shalguev OK, so you've actually proven yourself now that whatever is wrong for you is not a generic Vivaldi nor Ubuntu 20.04 bug. Thus maybe next logical testing step might be to create a secondary user profile in your "problem pc" GNOME, & see if future V updates therein also cause the same misbehaviour as your primary GNOME user account. If no, it narrows the root cause a little further to be something directly related to your current/primary GNOME user account.
I use KDE, for which there's a standard way to "reset" one's Plasma settings in a given KDE user account. Does a similar thing exist in GNOME?
PS: Oh, i was mixing up this thread with some others, so just realised that so far, i've not read herein that you have tested with a new Vivaldi profile. Have you? If not, then personally i'd take that step before trying the actual new GNOME account.
@guigirl thanks for your idea with a new profile (Vivaldi and then GNOME), but this issue happens only every 2 weeks and to set this experiment would be too much for me. For now I'm just fine with forcefully stopping the process.
ugly last edited by
Okay, so with the new snapshot out today, I was able to get an idea of when the CPU actually starts spiking.
I had the previous vivaldi-snapshot version running (2238.3). My update manager picked up the new update (2254.3). And I installed it while the old version of vivaldi-snapshot was still running. I updated from the update manager GUI in Linux Mint (I didn't run the apt upgrade command from the command line).
After the installation was complete, vivaldi-snapshot started the CPU spike. I did not close the old version yet. the vivaldi-bin process name shows the CPU spike.
So it appears that it does happen to the currently running version of Vivaldi, in response to the update. I don't have to close the old version for the CPU to spike. After I close the old version, the process still remains. I have to 'kill' the process manually. After that, no more CPU spike.
This sounds like it is related (could be the same issue) to my problem (posted in another thread).
After updating to the latest version (and rebooting before doing anything else), Vivaldi seems to just eat too much CPU.
I'm going to need to find the download for the previous version (3.6) and install that and see if the problem goes away.
@guigirl I was wrong when I said this never happens on my second Ubuntu 20.04 machine. I just didn't notice because its Cooler is not getting as angry as my laptop's one.
Today I updated Vivaldi while it was still running and the same behavior appeared again and I just rebooted my PC as Ubuntu advised.
@shalguev You probably won't like this post, but it seems entirely viable to me [as it's what i do]. Why persist with leaving your V still running, when you use your Ubuntu package manager to update it? Why not instead close V, update it, then launch it?
I'm having the exact same problem when refreshing or rescaling some websites.
It just lags up my whole machine. Using a Ryzen 7
It's noticeable worse with dev tools open.
I love the browser, and don't want to switch back, did you find a solution? @shalguev?
@ySomic I believe the issue of your browser is unrelated with mine, so probably you should google more on your scaling issue or create a new topic with all the details like CPU, URL(s) and moments when it happens.
My first idea - try to turn off hardware acceleration in your browser settings, but I'm not an expert here)
phenoman18 last edited by phenoman18
I have the same problem on Manjaro(KDE), but it happens every time i start Vivaldi, my laptop burns battery - unusable for me...
One of the threads is always on 100% when Vivaldi is running, after closing process names 'vivaldi-bin' remains active and uses CPU until I kill it manually...
Tried to disable and uninstall all of the extensions - didn't help
Today I've updated it - problem still here
Reinstalling doesn't fix issue
Switching to different browser for now.... hope all gets patched very soon - can't afford distro hopping or leaving KDE
On each report add:
- Vivaldi Version |
- Since when happens |
- OS / Version / DE |
Try on a New 's Profile:
- "Right side" |
Rename it as Tests or something related, and use it as a Clean Profile, to test without custom configurations that can alter the original operation.
Since the result, check:
- Active Flags / Experiments or Switches
- Ad Blocker - Tip
- Site Data
- Clean Cache
- Extensions - Tip
- Custom Menus
Or fill in a Bug Report and please, add the VB# to the topic for follow up.
Some useful links:
Forums Community Official Tutorials Official Help Forum Categories Modding Vivaldi Vivaldi Features Vivaldi Help Forum Markdown Panels | Engines Vivaldi Tutorials Issues Feature Requests ¿? Menus | Guides | FAQ Vivaldi How To Bug Reports
"Off Topic Tip"
Follow the Signature's Backup | Reset link.
Take the opportunity to start a Backup plan and even create a Template Profile.
I am also affected by this, on Uuntu 20.10. Reported as VB-80663.
@guigirl Used to happen to me on arch linux with swaywm (wayland tiling window manager).
Additionally to the 100% phenomenon, there can be a huge fluctuation in CPU usage (see e.g. https://forum.vivaldi.net/topic/53293/introducing-vivaldi-mail-in-technical-preview/333?_=1623579989665). I suspect M3 (calendar and/or mail) to be responsible for this.
Just noting this is till present and it does not affect only Snapshots - it also affects Stable versions.