I retested the cpu load with snapshot 4.2.2406.23-1:
Situation seems mostly unchanged. Only thing to note is, that after closing the last window of Vivaldi, all processes of Vivaldi are terminating after a while (in earlier days I had to manually terminate the processes as their shutdown lasted too long).
=> I can use the Calendar function for my own calendar in Google Workspace but not together with those of my co-workers - as in this case Vivaldi becomes too sluggish/unresponsive.
During my first sync of theses additional calendars my cpu load looks like this:
@npro said in H.264/AAC broken in the last update:
you can just delete that
Thanks, though as far as I remember it always comes back with an update
Interesting. The current iterations of scripts for stable and snapshot are not fetching and placing that file, as you can probably see for yourself by reviewing the code in update-ffmpeg. Perhaps you have some other package installed that places a file there (for Vivaldi to use??)? Though I do not know why it would given we no longer look in that location, as you can see check in the startup wrapper. Perhaps I forgot to give some package maintainer the memo that this file is no longer needed or loaded by Vivaldi?
This looks like a bug, as I can't reproduce such behavior on the latest Snapshot (although I'm on Windows). Perhaps it's Linux-related, so I'm moving this to the Support & Troubleshooting category since it's not a valid feature request anyway.
Please see how to troubleshoot issues and if you find a consistent way to reproduce your issue, report a bug in Vivaldi.
@thebitbandit said in CPU pegging in Ubuntu 20.04:
@ugly I did as you suggested and that has fixed the problem. Thanks!
Glad to hear it. Until the issue is fixed, one workaround is to make sure you close Vivaldi before you update. The issue only occurs if Vivaldi is running while you update.
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
Last Tabs - Chrome Web Store
Easy switch to recent tabs
Last Tabs is the extension for switch to the recent active tab with Alt+Z keyboard key. Supported for previously multiple active tabs and also support for multiple window.
The hotkey can be changed here: chrome://extensions/shortcuts
@mvamos said in "HTML5 'proprietary' media" error popup after upgrade:
Why would HTML5 be broken on an update??
Because some Chromium core code changed in Vivaldi and related codec/DRM lib has to be updated.
Current update to 4.2.2406.48 fixed such media errors with a automatic download after update.
@npro thank you for your time and effort.
So according to the info we're talking about a ~10-year old (Core 2 Duo I assume) Optimus laptop, right?
Having to kill the process in terminal doesn't sound good, I'd say stay with kernel 5.4 or 5.10 for the moment, don't use 5.14 as it's still very fresh imo.
So thought I. With 5.14 was just a test.
-Are the fans you are hearing those of the CPU or GPU? Or is there just one fan?
-Do you notice the same if you use the integrated GPU instead?
I think yes, but need to verify
-Did you test it with a clean profile, without extensions? For example from terminal vivaldi-stable --user-data-dir=/tmp/vivaldi-test-profile/ & (or troubleshooting help page)
-Try using nvidia's GL version instead of Google's by adding --use-gl=desktopto the above commandline (before & obviously).
-Try disabling the gpu completely with these switches: --disable-gpu --disable-software-rasterizer
Tried with all those flags. The manually killing of Vivaldi is now not necessary anymore. Appears to close properly now.
-Chromium browsers share a different engine to Firefox & Qtbrowser, try comparing it to at least Chromium, (better: Chrome)
I don't want install another Browser but will do so if other things are without success. tried this now with Opera and experience the same 2-5 sec. fan peaks on website load. So might be a chromium issue afterall?!
Also, make sure it's browser related and not to a thing in the system "hidden from your eyes" consuming CPU cycles, so compare Vivaldi's Task Manager with your System Monitor. You could also run journalctl -f to see what's happening real-time.
I'll try that