We will be doing maintenance work on Vivaldi Translate on the 11th of May starting at 03:00 (UTC) (see the time in your time zone).
Some downtime and service disruptions may be experienced.
Thanks in advance for your patience.
100% CPU Linux Mint
-
So, I've been reading about this issue in other threads, but I can't figure out how to deal with it. I need a simple explanation & solution. If I restart my computer, CPU usage is very low. Once I start Vivaldi, it maxes out on 2 of my 8 CPU's all the time. Even when Vivaldi is shut down, the CPU usage still maxes out 2 CPU's all the time. Does not happen with another browser. I'm happy to supply any info that might help.
Linux Mint 19.3 Cinnamon all updates.
Latest Vivaldi updates via apt
Dell Optiplex 7010 i7 16Gb RAM, Samsung SSD -
@felemur
Hi, I use Vivaldi on several systems with Linux and Windows and don´t have this issue.
There are two things I can think of, one is an extension on steroids, the other is a tab you start with.
You can check wich tab/extension is using your CPU with the internal task manager. Open it with Shift+Esc.
Please open chrome://settings and search for background, disable running applications in background.
This maybe solve the issue running CPU after closing >>Vivaldi.Cheers, mib
-
I've run into this issue intermittently on Linux Mint 20.x MATE as well. Disabling the 'Continue running background ...' functionality (chrome://settings/system) has helped. But, sometimes if weirdness in Vivaldi starts again I close Vivaldi and do a 'ps ax|grep -v grep|grep vivaldi' to check if any vivaldi processes are still running. If there are... I do a 'pkill -f vivaldi-bin' to kill the processes. Usually I have to run the kill command at least a couple of times to kill them all. Then launch Vivaldi again and usually all is well once again.
btw, this is on vivaldi-stable 4.x
. -
I run Linux Mint Cinnamon (just updated to 20.2).
I have seen issues with 100% CPU, but only when there is an update. Since I use the snapshot channel, the browser updates more often, so I see it more often than in the stable channel. But I did test the stable channel and found the same issue.
When a vivaldi-snapshot update appears in my package manager, and I update while Vivaldi is running, CPU usage will go up to 100% on one core during installation. CPU usage will stay at 100% after closing the browser. I need to manually kill the lingering vivaldi-bin process to get the CPU usage to stop.
After killing the process, there are no issues again until the next update.
If I update vivaldi-snapshot when the browser is not running, then there is no CPU issue.
I have not seen 100% CPU issues occur outside of updating.
-
Thanks for all the reply's. So far:
Disabling the 'Continue running background" via chrome://settings/system did not help.
I tried stopping all extensions one by one without any noticeable effect.
I have tried killing the process that my "System Monitor" shows under the processes as the ones still running after it is closed, but the problem comes back after Vivaldi is restarted - not right away, but soon. And..does not need to be just after an update.
I've taken a screenshot of the processes in the System Monitor when this issue is happening. It is always two Vivaldi-bin at 12% each that are the processes that pin 2 CPU's at 100%. Not sure if this is any help.
EDIT: I've just shut down Vivaldi, killed the two processes, and restarted Vivaldi at exactly 17:00 Saturday local time. I will see if I can determine how long it takes for them to come back.
-
@felemur
Hi, can you check the internal taskmanager if it come back, please?
System monitor does not show which process use CPU but internal does.Cheers, mib
-
OK, will do.
Oddly, it has not come back and it is 13.5 hours since I killed the 2 processes and restarted Vivaldi.
Maybe "ugly" is right regarding updates being at the core of the issue. Maybe last time I killed the processes, there was an update that I missed. I have the Linux Mint auto-updates turned on, and I had forgotten about that. If that is correct, then all I have to do is kill the 2 processes each time there is an update which is no big deal.
I will just keep an eye on this and post after the next update. As of now, so far, so good.
-
@ugly
I am starting to think you are right. See my latest post. Thanks. -
Ppafflick unlocked this topic on
-
Ppafflick moved this topic from Vivaldi for Linux on