Constant high CPU
-
Hi,
I just updated yesterday to 3.6.2165.40 (stable, 64-bit) on Manjaro (kernel 5.4 LTS, nvidia drivers) and I'm getting a strange problem: vivaldi seems to be maxing out one cpu core, and causing the fan to run, almost constantly. I've never seen vivaldi do this in the past (I've been running V since day-1).
In V's Task Manager the "Browser" entry is showing > 100.0 CPU usage almost constantly -- no other entries are even close to that.
In KDE's System Monitor (set to "all processes, tree") only the main parent/root V process is showing any significant CPU usage.
In addition to this, when I close V it doesn't exit (and the CPU usage remains high). Many sub-processes become zombies but the main process and a few others continue running.
killall vivaldi-bin
needs to be run 2X or 3X to get them all to exit.Aside from this everything appears to be working perfectly.
I have ~14 tabs open but all are hibernated (except the one I'm writing in). All the same tabs were open in the previous V version before I updated. And, as noted above, none of these (nor any extensions) are showing any significant CPU usage in the Task Manager.
I've been poking and proding, searching and trying different things (rebooting, tweaking settings) but nothing has worked so far. I also tried running V from the command line but I did not see any output that seems related.
I'm not sure what to try next and I'd really appreciate some help.
The build packages from Manjaro are
community/vivaldi
andcommunity/vivaldi-ffmpeg-codecs
.Has anyone else experienced this? Any ideas on how to figure out what's going on? Is there any way to get V to report more diagnostics?
Thanks!
~ray
PS: Almost forgot: the option to keep V running after exit is disabled; sync has completed and is idle.
-
@raybert said in Constant high CPU:
In addition to this, when I close V it doesn't exit (and the CPU usage remains high).
Check chrome://settings/system - Disable 'Continue running background apps when Vivaldi is closed'
Restart Vivaldi
the "Browser" entry is showing > 100.0 CPU usage almost constantly
Does Vivaldi://gpu show that hardware acceleration is active or not?
-
@TbGbe said in Constant high CPU:
@raybert said in Constant high CPU:
In addition to this, when I close V it doesn't exit (and the CPU usage remains high).
Check chrome://settings/system - Disable 'Continue running background apps when Vivaldi is closed'
It is disabled. (I added that to my post but we crossed...)
the "Browser" entry is showing > 100.0 CPU usage almost constantly
Does Vivaldi://gpu show that hardware acceleration is active or not?
It is not and the blacklist override is disabled.
Graphics Feature Status Canvas: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Out-of-process Rasterization: Disabled OpenGL: Enabled Hardware Protected Video Decode: Unavailable Rasterization: Software only. Hardware acceleration disabled Skia Renderer: Enabled Video Decode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated
-
Hi, maybe you are using some unsupported flags? Also I assume you are not on Wayland. Check if the same behavior can be observed in a new clean testing profile. You can launch one with
vivaldi-stable --user-data-dir=/tmp/vivaldi-test-profile/
for example. -
@npro said in Constant high CPU:
Hi, maybe you are using some unsupported flags? Also I assume you are not on Wayland. Check if the same behavior can be observed in a new clean testing profile. You can launch one with
vivaldi-stable --user-data-dir=/tmp/vivaldi-test-profile/
for example.Hi,
Thanks for the suggestion. I tried it and the exact same problem happens (high CPU & won't quit).
BTW, I think I failed to mention this earlier but when I try to close V the window does close like it is shutting down but the processes continue running in the background. (I'll update my initial post with that info.) When running from the shell (like I did here) it takes two ^C's before it quits.
Thanks again,
~ray
PS: And you are correct, I am not running Wayland (but I live near it... Wayland, MA, that is...
PPS: Apparently the forum won't let me edit my OP any more... oh well...
-
Please see this: https://forum.vivaldi.net/topic/57147/it-s-about-time-vivaldi-browser-snapshot-2202-3/77?_=1615496000149
I have had a similar issue, still occuring at times, which I could relate to calendar / mail. You should press Shift+Esc in vivialdi and have a look which process actually needs all the CPU ressources, maybe just post a screenshot. And probably you should report this as a bug. https://vivaldi.com/bugreport/
-
@jumpsq said in Constant high CPU:
Please see this: https://forum.vivaldi.net/topic/57147/it-s-about-time-vivaldi-browser-snapshot-2202-3/77?_=1615496000149
I have had a similar issue, still occuring at times, which I could relate to calendar / mail. You should press Shift+Esc in vivialdi and have a look which process actually needs all the CPU ressources, maybe just post a screenshot. And probably you should report this as a bug. https://vivaldi.com/bugreport/
Thanks for suggestions.
However, (a) I am running stable, not snapshot, and (b) I did already report what the Task Manager is saying (> 100.0 for 'Browser'; much less for all others; most are 0.0 most of the time).
I would feel better about reporting this as a bug if I could find a cause and determine it is really a bug. But, if no solution appears and the problem persists, I will probably eventually report it anyway.
Thanks again,
~ray
-
Check the post here: https://forum.vivaldi.net/post/448442
It may help in killing the processes as depending how the process is created makes a difference on when it is to be Killed.
-
@greybeard said in Constant high CPU:
Check the post here: https://forum.vivaldi.net/post/448442
It may help in killing the processes as depending how the process is created makes a difference on when it is to be Killed.
Thanks. I did already see that post. As I noted, I am using
killall
to end the processes and this works fine. I either run V from a.desktop
file (icon) via KDE or from the command line, and the result is the same: it never exits, even when running it with a fresh profile (using--user-data-dir
).Since it takes multiple times to kill it I have now been using:
while killall vivaldi-bin 2>/dev/null; do sleep 1; done
I also just tried reinstalling it (after ensuring no processes were left running) but no change.
I used to leave it running all the time but now I'm shutting it down when I stop using it (to give my cpu a break) and am using Firefox more often.
-
@raybert Sorry to hear that.
I am running PCLinuxOS and have no problems even with my old memory shy laptop. -
@greybeard said in Constant high CPU:
@raybert Sorry to hear that.
I am running PCLinuxOS and have no problems even with my old memory shy laptop.neither have I until 2 days ago...
-
I have noticed this issue a few times. But not during regular use of the browser.
I use the snapshots. There have been a few updates recently where after I update and restart vivaldi-snapshot, I do get one vivaldi-bin process that maxes out one of my CPU cores. Even after closing vivali-snapshot again, the process does not go away and I have to kill the process manually. After that, everything seems to work fine.
But this only seems to happen when I upgrade. I have not noticed it at any other time.
-
@ugly said in Constant high CPU:
I have noticed this issue a few times. But not during regular use of the browser.
I use the snapshots. There have been a few updates recently where after I update and restart vivaldi-snapshot, I do get one vivaldi-bin process that maxes out one of my CPU cores. Even after closing vivali-snapshot again, the process does not go away and I have to kill the process manually. After that, everything seems to work fine.
But this only seems to happen when I upgrade. I have not noticed it at any other time.
Thanks. For me it's happening all the time, every time it runs, even before I do anything, even after cleanly killing it and regardless of updating or whatever. And it is constant, not spiking. And, as mentioned, it still happens when running with brand new profile (no extensions, changed options, or open tabs). So there's clearly something weird before. It looks very much to me like a runaway loop in the main process, but I've no clue what could be causing it.
-
I think the issue is solved. Thanks to everyone for their help.
Although I had already tried reinstalling it (which didn't help), I decided to try completely uninstalling it (along with the ffmpeg and widevine packages) and then cleaning away any lingering reference to it (other than my profile directory), and then reinstalled it, and that seems to have fixed it. I have no idea why that worked, but it did, so, great!
Thanks again,
~ray
-
@raybert I am experiencing the same scenario, same issue. I will try to completely reinstall and see if that fixes it.
-
Well, I did reinstall before and have those issues again. Not constantly, but if they arise, then there are two processes at 100% each occupying 2 cores even minutes after Vivaldi is closed (and sometimes I have to kill them manually).
Good luck!
-
I have just experienced this after upgrading to 3.7. I had to kill my Vivaldi and start again.
When this happens again I will report it and try to do some screenshots of the htop.
Vivaldi: 3.7.2218.45 (Stable channel) (64-bit)
-
After Vivladi had been closed withCtrl+Q
for 5 minutes. Snapshot from two days ago. I may use unsupported flags + wayland, but since there are more reports, it does not seem to be the cause here. -
@Gwen-Dragon As mentioned, I doubt it's the cause, and as reported previously, I think it is (partially?!) related to M3 and to the calendar more specifically.
Let's just hope it is resolved somehow. Reports from other users can only be helpful in this regard.
-
Info about the vivaldi (and params):
Vivaldi 3.7.2218.45 (Stable channel) (64-bit) Revision fd6604a1bdbe9da3e648d7e601352c87e0259dc6 OS Linux JavaScript V8 8.9.255.20 User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.91 Safari/537.36 Command Line /usr/bin/vivaldi --use-gl=desktop --profile-directory=Default --flag-switches-begin --enable-gpu-rasterization --enable-zero-copy --ignore-gpu-blocklist --disable-smooth-scrolling --flag-switches-end --origin-trial-disabled-features=SecurePaymentConfirmation --save-page-as-mhtml Executable Path /opt/vivaldi/vivaldi Profile Path /home/mp/.config/vivaldi/Default
Maybe one of these flags is responsible ?