Vivaldi uses 100% of one of CPU cores on each update via Software Updater
-
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.
-
So today I got a message this is fixed in a stable update. I updated and it happened again but I guess the fix means it will not happen on the next update - let's see:-). Hopefully it is fixed!
-
@felagund Yes, same for me on three office PCs.
Logout as Linux user did not help and zombies were running in the wild. regular users need to terminate by force withkill
orksysguard
– not really user friendly imho. -
Let's hope it was the last time!
-
@felagund Yeah!
-
Same problem here, running on PopOS 21.04.
Was forced to pkill the process, since a zombie was still running after closing the browser.Hopefully the new update will fix the issue
-
️ The fix prevents updates coming after version 4.3.2439.65 to cause a 100% CPU issue.
-
Had the same issue - stopped after disabling vivaldi://flags - accelerated 2d canvas- Hardware-accelerated video decode & encode