Brave has slow choppy scrolling in Google News. Problem is about a week old
Visit Google News/US or /World. Occurs only in Google News and only on the Brave Browser
Smooth fluid scrolling.
Version 1.62.156 Chromium: 121.0.6167.139 (Official Build) (64-bit)
Same problem with Google news on Macbook Air. It’s smooth scrolling at first but then becomes choppy as I scroll down a ways, just enough to make difficult to read, and doesn’t recover regardless of how far I scroll or how long I wait. Works smoothly in Safari. If I quickly scroll down through everything until I finally reach the end, I can then go back to the top and scroll through all the content smoothly.
What I see is it’s difficult to read while slowly scrolling through, have to stop incrementally to read the headlines. Working smoothly, I can easily read as I scroll. This morning it was smooth in the beginning, then choppy, then smoothed out again, then choppy the rest of the way.
Same issue on my Dell PC under Windows 10, plus when I look then I find that that tab is using 20%-25% or more of all CPU cycles. Pages work fine on Firefox.
Same issue for me. started about a week ago. google news pegs cpu usage around 15% by just having the tab open. switching tabs instantly drops usage. switching back and right back up. scrolling is very clunky the further you go. turning off shields and disabling extensions has no effect.
Brave version
Version 1.62.156 Chromium: 121.0.6167.139 (Official Build) (64-bit)
I have a work around that seems to work. it’s a tiny bit inconvenient but it helps. I simply preload everything by scrolling everything at once right to the end. Once Google is done loading which seems to be faster everything scrolls smoothly.
Sidenote: if I go into Task Manager, there are anywhere from 6 to 10 instances of Brave running at the same time. There is a lot of memory usage and CPU usage.
I think I figured out the issue and why it spans across PC’s and browsers. It may have to do with too many hidden sources. I cleared out all my hidden sources and the issue seems to have gone away.