Solved High CPU usage

rigo

134550 90.1 1.9 1215720212 307836 ? Sl 11:10 9:43 /opt/vivaldi/vivaldi-bin --type=renderer --string-annotations --crashpad-handler-pid=134189 --enable-crash-reporter=,stable --extension-process --change-stack-guard-on-fork=enable --lang=en-US --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=24 --time-ticks-at-unix-epoch=-1734499472995008 --running-vivaldi --launch-time-ticks=189977490794 --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,6695752664286728731,9110322397883578851,262144 --variations-seed-version

rigo

Will preserve that profile for debugging and move on with a new profile.

DoctorG

@rigo Duplicate Default/ folder to Default-BACKUP/
In Default/ delete all except:

History
Login Data
Sessions/
Bookmarks
Notes

Start Vivaldi.
Better now?

DoctorG

@rigo Could be a broken extension or with cryptomalware.

rigo

I have removed all extensions to no avail (wasn't using any except zotero anyway) so I would rather opt for your option with cryptomalware somewhere that infected the profile.

rigo

@DoctorG said in High CPU usage:

Duplicate Default/ folder to Default-BACKUP/
In Default/ delete all except:

This did the trick, CPU back to normal on this profile. The culprit was not in Default, but in Profile 1.

DoctorG

@rigo And missing something in profile?
You need to make some new settings.
And if you use extensions, try to add one and test CPU usage, and next extension and test, and so on - to reduce risk to get some bad extension again.

rigo

While we are at it. Can you tell them that Ctrl-F12 for settings collides with "Show Desktop" in KDE Plasma?

DoctorG

@rigo said in High CPU usage:

Ctrl-F12

I think that is known issue.

Can not be changed, browser can not detect with shortcuts are used globally in Desktop Environment.

//EDIT: I changed/removed shortcut in KDE settings to solve this.

ghpy

As I started the topic (and lost track of it) I'd like to mention that with some Vivaldi version the problem was solved for me. As it now seems to be solved for rigo as well, I will mark this topic as solved (at least I try, it's a bit confusing the way it works).