vivaldi-bin goes to 100% CPU after maintenance [SOLVED at 4.3.2439.71]
-
I'm running Vivaldi 4.0.2312.27 on MX Linux 19.3 .
If I leave Vivaldi up and running while the MX Linux package upgrader runs and Vivaldi gets upgraded (was on 4.0.2312.25 a few hours ago), I believe it's then that vivaldi-bin goes to 100% CPU; I know it does that after I exit Vivaldi, and then I have to kill vivaldi-bin and restart Vivaldi to get it back to its normal low CPU utilization levels.
Is there some sort of setting/switch to prevent this? My laptop starts getting hot.
-
@durhammer Of course there is no setting for this, it's a bug. You need to reproduce it in a way that can be reported to the team for fixing.
Please read:
carefully and report the bug to Vivaldi bugtracker
-
This has happened to numerous people for some months now on linux, but I have no idea how to reproduce it.
Have you enabled and/or do you actively use calendar and vivaldi mail? -
@pathduck Yeah, I didn't really think there would be a setting, but you never know!
Okay, so after reviewing the "Help us..." page, I don't see many of those checkbox items that I need to tweak in this case. Third party cookies are only disabled for incognito mode, which I don't use. I do have a number of extensions, but this would seem to be a core issue, not any UI thing. And I'm already on the most recent MX Linux version of Vivaldi available, and it's upgrading that causes the problem. Please correct me if I'm wrong and advise what essential tweaks need to be done before reproducing this problem.
I will just have to wait a while until another upgrade is pushed out (could be soon again -- this is the third in a week already!). Thanks for the advice.
-
@durhammer said in vivaldi-bin goes to 100% CPU after maintenance:
I do have a number of extensions, but this would seem to be a core issue, not any UI thing.
How do you end up with that conclusion? Buggy extensions account for well over 90% of issues reported by users here.
Especially important is testing in a clean profile with nothing changed.
-
I ran into this situation just recently as well in vivaldi-stable 4.x in linux... 100% CPU, fan which normally doesn't run at all was tacking high RPMs, temp at 90 degs C when normally it runs at around 40 degs C.
Closed Vivaldi and noticed that vivaldi-bin was still running. I looked to see in 'Settings' for the 'keep running in background' switch but couldn't find it. So instead tried going to 'chrome://settings' from the 'Address field' and searched for 'background'. Scrolling down to find: 'Continue running background apps when Vivaldi is closed' which I disable and which thus far has stopped all the weirdness I was experiencing in vivaldi.
So. You might might want to tried disabling 'Continue running background apps when Vivaldi is closed' if it isn't disabled already? The easiest way to get there is by inputting: 'chrome://settings/system/' in the address field and hitting <Enter>.
End note: Do NOT try to use: 'vivaldi://settings/system/' ! It does not get you to the page of which I've typed about here.
. -
@martywd Thanks, Marty. And yep, that setting indeed already is OFF. Interesting, but in a way not at all surprising, is that when I enter that URL, while you are quite correct about the page that is opened, what the browser address bar shows IS the "vivaldi://settings/system/" URL. Crazy world.
@Pathduck Thanks, Stian. I weeel comply!
-
@jumpsq Actually, this happened to me long before I knew about or enabled the Beta features.
It was only with a recent upgrade where I started looking at the "what's new" or some similar, and saw the bit about mail and calendar integration that I took the bait.
Started having issues/questions (the thing about Google calendar and Gmail integration needing a Google security tweak, for instance) that I joined the forum and started posting questions. Figured it was about time to ask about this one. But again, it was happening well before activating the betas (might not have even been hidden in the guts for all I know).
So the only way I know to "reproduce" it is to wait for another MX Linux upgrade package notification. Then guess I'll have to do all the recommended things (@Pathduck can correct me if this isn't correct):
- Disable all my extensions.
- Clear cookies and
creamcache. - Restart the browser.
- Accept the upgrade while Vivaldi is running.
If I need to set up a new profile and use a standalone version, someone please let me know ASAP (and how to), because otherwise, I'd have to wait until another package upgrade comes down the pike....
The problem for me has been only when doing this last step, and even after closing Vivaldi, vivaldi-bin remains spinning at 100%.
-
Hmmm... @martywd and @jumpsq (if you know) -- thinking about @Pathduck 's suggestion about buggy extensions -- just what extensions do you (or whoever it has happened to) use? I'm using:
- Join by joaoapps (essential to me to connect to my 'droids)
- ToDo by Microsoft (oddly enough, for recipe organization)
- Print Friendly & PDF (I do use this quite a bit)
- BrainTool! (don't know why I have it, don't really use it)
- YouTube Auto HD + FPS (not sure if I need this either)
- uBlock Origin (dunno if this is so necessary in Vivaldi but I like the insurance)
- Life360 Chrome Extension, which I just now removed since they yanked the web access anyway, but this was happening before I even knew about this extension.
- Bitwarden (which I find quite useful and worthy, naysayers be damned!)
- uMatrix (which I'm also wondering if I need at all in Vivaldi)
- DuckDuckGo Privacy Essentials (likewise?)
I'd be interested to see what other folks have that also have the 100% CPU problem after upgrade.
-
@durhammer Yes, testing the upgrade process on Linux is probably not going to be as easy as it is on Windows, where I can just install a standalone release of any version anywhere.
Old releases can be found here, but looks like only DEB packages:
https://vivaldi.com/download/archive/No idea if your package manager lets you roll back to older packages or even if Vivaldi is controlled by the package manager.
You could in theory make a backup of the
Default
user profile folder, then roll back the version for testing and recreate the issue. Not even sure a backup is strictly needed, as there's been so little changed between the last releases.Ed: And that's a lot of extensions. Generally, if you don't know if you need an extension, you don't need it.
-
@pathduck Help. Don't even know what the Vivaldi "profile" is. I see "vivaldi" FOLDERS under ~/.cache and ~/.config but don't know what they hold. Not sure what I would specifically need to do to accomplish this. Should be able to do everything else.
Yes, Vivaldi is managed by the MX Linux package manager (it was installed that way, IIRC). MX Linux package manager does have a couple of other sources, maybe one of those is older (there are Deb back-ports). Not sure how to roll back versus get a back-port, or even if that makes sense. But I don't know if it then would hit me with an upgrade at any reasonable time frame. I think for now, I'm just going to have to try this without the "standalone" version. (But I guess I could ask what might be doable on the MX Linux forum. Hmmmm....)
And yeah, I know I have too many extensions and am in the process of pruning them (as noted earlier, already took one out of commision). I'm thinking I will next remove DDG, uMatrix, BrainTool!, and the U Toob thingie, and only add back anything that looks like it made something work better. I probably can also get rid of the M$ ToDo thing, since I have the app on my 'droids and can send whatever files like PDFs to them or URLs via clipboard, all sent by Join, which I can't get rid of (until testing time, anyway).
-
@durhammer You'll find your profile path in
vivaldi:about
(from address bar or QC). Otherwise, Menu โ About Vivaldi. -
@hlehyaric Ah cool, so it's ~/.config/vivaldi/Default . Thanks! BUT!!! What the heck do I do with the contents besides just "make a backup" ... and "roll back the version for testing"? Don't quite understand just what steps are needed. Messing with bits and pieces on Linux can give interesting results....
-
@durhammer Copy
Default
orvivaldi
(in ~/.config) & paste it wherever you want outside a Vivaldi folder (somewhere where you can find it easily.@Pathduck has suggested you to install an older version of Vivaldi (replacing your current one with an older one, hence your profile backup, just in case).
-
@hlehyaric Okay, I've copied out the Default folder to a different location. Do the contents get totally overwritten when doing a package update, or does it take a complete install?
I did post the question in the MX Linux forum, and it does appear that I can use the Synaptic "Force" feature to force a different version. Apparently I can get back from .27 to .25 -- or maybe all the way back to .21 --
https://repo.vivaldi.com/stable/deb/pool/main/
...and I should be able to "ask" for an update with "sudo apt update". Actually, from re-reading the responses, it looks like it might be possible to do the standalone install of one of the older versions found above rather than doing the Synaptic Force action. I'll try that first.
-
@durhammer Anyway, it's better to backup your profile.
If a standalone install is possible, of course try it first. -
Okay @hlehyaric @jumpsq @martywd @Pathduck I have
- Copied the Default profile folder out to holding pen
- Disabled all extensions
- Cleared all cookies and cache
- Closed Vivaldi (? might not be right sequence -- see later)
- Forced the downgrade from .27 to .25
- Brought up Vivaldi again
- Verified that version is .25
- MX package updater already detected the upgrade need
- Let packaage updater upgrade to .27 while Vivaldi open
- Checked output of top command to see that vivaldi-bin indeed was pegging 100%
Took screen shots of "steps" 7, 8, and 10 with Vivaldi both open and "closed." Unfortunately (?), top shows TWO vivaldi-bin processes at, near, or above 100%, so maybe the order isn't quite right or some such. BUT -- is this description and the screen shots going to be enough for the bug report? Don't want to do the report if I'm going to need to do it again and again.
Also, I keep getting prompted to sign in to Google to "continue to Vivaldi" -- I presume that's some event that happens periodically? Calendar or Mail perhaps but the profile is gone?
-
@durhammer After backing up the Default profile, just delete the original to ensure a completely clean profile. Then downgrade and try the update again.
I'm sorry this is so complicated. The whole point is to verify if the high CPU also occurs with a completely clean profile after update. If so you have a stronger case for making a bug report that can actually be reproduced by the team and fixed.
Also, after launching Vivaldi and noting high CPU, open V. Task Manager (Shift+ESC) and then correlate the Process ID with the PID of the
vivaldi-bin
causing high CPU. What process is it and what's its full command line? -
@pathduck Stian, remember that I DON'T launch Vivaldi after the upgrade -- it's left open. But that's a great suggestion to ensure that the display PID and the 100% CPU PID are one and the same.
Okay, like Steely Dan sang, I guess I can GO BACK, JACK, AND DO IT AGAIN!
-
This is a problem that has been noticed by a few people for a while now. Here is a previous thread on this issue: https://forum.vivaldi.net/topic/59122/vivaldi-uses-100-of-one-of-cpu-cores-on-each-update-via-software-updater?_=1623710419770
It's much easier to reproduce when you're on the snapshot channel, simply because you'll get updates more often.
It looks like another user has reported the bug: VB-80663