Closed intuser closed 1 year ago
Probably related: Visiting https://www.spiegel.de/politik/deutschland/fridays-for-future-sorgt-mit-tweet-ueber-grosseltern-fuer-aufregung-a-1302665.html the page loads (very slowly). But scrolling down twice or so it turns grey and nothing moves. (I can change to other buffers though.) The problem appears with other pages of this website too.
This could be a WebKitGTK issue. Can you test with Epiphany or any WebKitGTK-based browser see if you can reproduce?
I tested epiphany, with a mixed result: CPU use simply having www.spiegel.de in the current buffer is relatively hight with this browser too. (But devided between gnome-shell and WebKitWebProces.) During loading the CPU use also is quite high, but much lower than with next. But the reason might be that epiphany seems to come with an adblock system enabled and there are almost no ads. (That's of course great. But I don't see how I could change it for testing purposes.)
I've been thinking about integrating a new optional JS adblocker in addition to the content blocker we have now, can you try disabling the adblocker and see if the performance is the same?
I disabled the adblocker in epiphany and things turned as bad (or worse) as they are in next. So the adblocker in epiphany makes it usable with pages like www.spiegel.de and something like that in next would be an great improvement!
Ah ok! Very good to know! Thank you for the feedback and report!
@intuser Is it still a problem on master with a recent WebKitGTK+ (2.28.2 or above)?
The ad-blocker is discussed in #32. One way to implement it would be to support WebExtensions first (#464), this would give us uBlock for free I believe.
Yes. I now have WebKitGTK+ 2.30.3 and nyxt 2 and the problem continues.
Please try our latest release. This is probably an issue that is outside of our scope.
If I visit www.spiegel.de and keep it as the current tab the WebKitWebProcess uses a lot of CPU. (Around three to six times of for instance waterfox. It's enough to keep my fan working.) Loading a new page on that site again uses much more CPU than waterfox. (Browsing is notably slower therefore.)
Information