Background Page causing high CPU usage

[DoctorG]

@ambroz09 said in Background Page causing high CPU usage:

Yes, I have recently subscribed to one single RSS feed for the first time.

Can you share the URL?

[DoctorG]

@ambroz09 Can not reproduce your issue.

I tested your feed on Debian 12 KDE (in a VM with 2-Core Intel and slow GPU) and could not see any high CPU usage with Vivaldi 6.8.3381.48.
Dispay of a feed item get a spike of 15-20% for very short time, and then 2%..
I tested without having any extensions installed.

And the feed is valid and without any content consuming such high CPU as in your case.

What happens if you check in a fresh test profile?
Run as user in shell/Terminal this command
vivaldi --user-data-dir="/tmp/TESTVIVTEST" &
Close Welcomne screen
Open Settings → Feeds
Activate use of Feeds
Add you feed

Dose that cause similar much CPU?

[ambroz09]

@DoctorG thanks for testing.

The problem is reproducible on my system.

I'll check per your instructions.

[DoctorG]

@ambroz09 I updated my post.

[ambroz09]

@DoctorG
(1) the problem is always reproducible on my working copy of Vivaldi.

(2) there is no problem on the testing (fresh) copy of Vivaldi.

[DoctorG]

@ambroz09 Removing the subscribed feed, restart Vivaldi and add gain does not help?

[ambroz09]

@DoctorG
On my Vivaldi configuration if I remove the feed and restart Vivaldi, Background Page process is back to 0% CPU.

If I then subscribe to the feed back again, Background page within seconds jumps to at least 94% CPU and stays there.

[DoctorG]

@ambroz09 Do you run Wayland or X11?

I will test now on Ubuntu 22 LTS.

[ambroz09]

@DoctorG
wayland

[ambroz09]

But there must be some problem in the configuration of "my" Vivaldi as the testing (new) version of Vivaldi was working without problems.
Background Page stayed at 0% after adding a RSS feed.

[DoctorG]

@ambroz09 I see same results with Ubuntu 22.04 LTS Wayland as on Debian 12 KDE X11.

[DoctorG]

@ambroz09 I agree, as the test profile runs fast theer must have been happend something strange with your original profile.

[DoctorG]

@ambroz09 I suggest a hard workaround:
Backup your profile ~/.config/Vivaldi/
Start Vivaldi
New Tab (not the feeds or mail!)
Menu File → Export → Feeds
Save OPML file on desktop
After you have exported, delete all feeds in Settings → Feeds
Restart Vivaldi

Check CPU usage now
If it is low, try a re-import of feeds
Menu File → Import from files and apps → Select Feeds (OPML) file
Select the previously saved OPML file and import

Does that help?

[DoctorG]

@ambroz09 If you use extensions, for a test, try to start Vivaldi as
vivaldi --disable-extensions &

[ambroz09]

@DoctorG I did as requested.

Deleted all feeds.
Restarted Vivaldi without extensions.

Result:
As soon as I enter a feed (any feed - this time I tried BBC News feed) Background Page process shoots from 0 to 100% CPU.

I guess I'll have to do without feeds on Vivaldi.

Thanks for your time and effort, much appreciated.

[DoctorG]

@ambroz09 And if you try X11?
Do you use Vivaldi deb-package or Flatpak?

[ambroz09]

@DoctorG Vivaldi .deb.

[DoctorG]

@ambroz09 I have no idea where such comes from.
Perhaps mail search database.
Can you please click in statusbar on Envelope → Cogwheel → Rebuild Mail Search Database and wait?

Do you have Settings → Webpages → Use of Hardware Acceleration active?
Can you post content of section Graphics Feature Status of page vivaldi://gpu here?

[ambroz09]

@DoctorG

(1) about mail search database: I don't have any mail configured in Vivaldi

(2) about Use of Hardware Acceleration active: Yes, it is active

(3) about vivaldi://gpu
Graphics Feature Status

• Canvas: Hardware accelerated
• Canvas out-of-process rasterization: Enabled
• Direct Rendering Display Compositor: Disabled
• Compositing: Hardware accelerated
• Multiple Raster Threads: Enabled
• OpenGL: Enabled
• Rasterization: Hardware accelerated
• Raw Draw: Disabled
• Skia Graphite: Disabled
• Video Decode: Hardware accelerated
• Video Encode: Software only. Hardware acceleration disabled
• Vulkan: Disabled
• WebGL: Hardware accelerated
• WebGL2: Hardware accelerated
• WebGPU: Disabled
• WebNN: Disabled

[sdgreene]

I'm encountering this issue on Manjaro as well. Usage is around 180-260%.

I have an AMD Ryzen 3900x and Radeon 6800XT on Wayland (X11 seems to behave the same). 32 GB RAM
KDE Plasma 6.0.5
KDE Framework 6.4.0
Qt 6.7.2
Kernel 6.9.12-1-MANJARO

Disabling Mail, Calendar, and Feeds made no difference. Rebuilding Mail database did nothing to the usage after it was complete.

I have hardware acceleration disabled because for some reason that flag syncs (which is insane because not all systems are the same and that should absolutely be profile/hardware specific, not a syncable flag). But I'll try switching that on to see if it makes a difference.

Pre-hardware acceleration enabled report:

Graphics Feature Status

• Canvas: Software only, hardware acceleration unavailable
• Canvas out-of-process rasterization: Disabled
• Direct Rendering Display Compositor: Disabled
• Compositing: Software only. Hardware acceleration disabled
• Multiple Raster Threads: Enabled
• OpenGL: Disabled
• Rasterization: Software only. Hardware acceleration disabled
• Raw Draw: Disabled
• Skia Graphite: Disabled
• Video Decode: Software only. Hardware acceleration disabled
• Video Encode: Software only. Hardware acceleration disabled
• Vulkan: Disabled
• WebGL: Software only, hardware acceleration unavailable
• WebGL2: Software only, hardware acceleration unavailable
• WebGPU: Disabled
• WebNN: Disabled

Problems Detected

• WebGPU has been disabled via blocklist or the command line.
  Disabled Features: webgpu

• WebGL2 has been disabled via blocklist or the command line.
  Disabled Features: webgl2

• Accelerated rasterization has been disabled, either via blocklist, about:flags or the command line.
  Disabled Features: rasterization

• Accelerated video encode has been disabled, either via blocklist, about:flags or the command line.
  Disabled Features: video_encode

• Accelerated video decode has been disabled, either via blocklist, about:flags or the command line.
  Disabled Features: video_decode

• WebGL has been disabled via blocklist or the command line.
  Disabled Features: webgl

• Gpu compositing has been disabled, either via blocklist, about:flags or the command line. The browser will fall back to software compositing and hardware acceleration will be unavailable.
  Disabled Features: gpu_compositing

• Accelerated 2D canvas is unavailable: either disabled via blocklist or the command line.
  Disabled Features: 2d_canvas