Vivaldi uses 100% of one of CPU cores on each update via Software Updater
-
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.
-
I'm having the exact same problem when refreshing or rescaling some websites.
It just lags up my whole machine. Using a Ryzen 7It'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)
-
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 issueSwitching to different browser for now.... hope all gets patched very soon - can't afford distro hopping or leaving KDE
-
Hi,
--
Please,
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.
--
Also,
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.
Windows 7 (x64)
Vivaldi Backup | Reset + Extra Steps -
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.
-
Another update here, same issue on both my Ubuntu (MATE) 18.04 machines, running Vivaldi stable. Currently on
4.1.2369.21 (Stable channel) stable (64-bit)
but this has been happening at each update for a long time. -
For the record, an issue here as well:
Debian 10.10, XFCE (my migration to new hw running bullseye, almost complete)
Commandline: apt-get upgrade
Upgrade: vivaldi-stable:amd64 (4.1.2369.18-1, 4.1.2369.21-1)Yes, Vivaldi was running when I initiated update. Will close next time.
FWIW: Haven't had a problem updating any other apps while in use. -
This is constantly happening each and every Vivaldi update. I need to kill "vivaldi-bin" process right after updating the package via apt.
-
Ugrade by
sudo apt upgrade
works nice for me, i tested on Debian 10.10 KDE 5 & Ubuntu 20 LTS GNOME & Ubuntu 21 and I got no 100% core usage after update. -
I have noticed the same problem: every time I update V one CPU core goes to 100% until I manually kill it. I haven't tried closing V, updating, and reopening V yet. I always do my updates with
sudo apt upgrade
and it still causes the problem. I'm running Ubuntu 20.04 LTS -
I have the same problem on both of my kde neon (ubuntu lts 20.4) installations after every update. Need do hard kill the main process.
-
@notz Well afaik a binary does not update itself while running so what's the point of leaving it open while upgrading...
P.S someone lock this thread pls, it's getting ridiculous already.
-
@npro said in Vivaldi uses 100% of one of CPU cores on each update via Software Updater:
@notz Well afaik a binary does not update itself while running so what's the point of leaving it open while upgrading...
P.S someone lock this thread pls, it's getting ridiculous already.
How do you update your system? Shutdown, boot with an live media login to your system and update?
Everybody is updating his running system (and security updates are applied automatically in the background). Also it's working on every other browser chrome, firefox, brave. So why not on vivaldi?
-
@notz said in Vivaldi uses 100% of one of CPU cores on each update via Software Updater:
How do you update your system? Shutdown, boot with an live media login to your system and update?
Everybody is updating his running system (and security updates are applied automatically in the background). Also it's working on every other browser chrome, firefox, brave. So why not on vivaldi?Some updates are safer being applied from tty (better: virtual consoles) because you can brake your system if you upgrade Xorg, systemd, nvidia, etc and Xorg for some reason breaks in the middle of the update process.
You are not upgrading your Vivaldi version = climbing the build number = getting the security updates if you don't restart the browser, if you don't believe me check your
vivaldi://about
version before and after the update, and maybe if my words have no credibility then Arch people's words are better:Restart or reboot after upgrades
Upgrades are typically not applied to existing processes. You must restart processes to fully apply the upgrade.https://wiki.archlinux.org/title/System_maintenance#Restart_or_reboot_after_upgrades
-
@npro I'm aware of that. I know what I'm doing, but I also know what a common user is doing: Updating with the graphical package manager, then he might reboot and he will always run in to this issue.
It's a bug and should be solved. End of it. If don't think that's the case then close the thread.
-
This occurred to me on version 4.3.2439.63 (Stable channel) stable (64-bit).
I'm using Kubuntu 20.04.3 LTS. I used graphical application manager (Discover) to update). I had vivaldi running when the update was happening.I remember this happened to me once earlier as well. I just had killed vivaldi-bin and assumed it was some one time issue.
Now that I faced the 100% cpu issue again, I searched and landed on this thread.
Let me know if I can give more information or post something that can help you identify the issue.