Bug 171789 – [GTK] High CPU usage w/o interaction, w/o javascript

• Status: NEW
• Component: WebKitGTK

[ManDay]

I noticed that at least on the following webpage:

https://www.notebookcheck.com/Test-HP-Spectre-x360-13-Convertible.180988.0.html

MiniBrowser from 2.16.1 has a high CPU usage, constantly, even without interaction (the window is not mapped) and JS disabled.

[ManDay]

I've tried this under weston and sway, and it appears that under weston (when on a different desktop, i.e. the window unmapped), the CPU usage is about 14% constantly whereas with sway (different desktop), the usage is about 40% constantly, and sway, too requests more CPU than weston.

I guess if no one can reproduce this then this is likely to have to be a problem more related to sway than to WK (there have been various problems with GTK in the past which appeared only or more frequently in sway than in weston).

The CPU is an i5-6267Z (4 hyperthreaded cores)

[ManDay]

i5-6267U

[Michael Catanzaro]

I can't reproduce this.

[ManDay]

It's

webkitgtk 2.16.1
weston 2.0.0-73-geca5cca
gtk 3.22.12

for me and when, for example, I open this bug with javascript enabled, turn javascript off (through MiniBrowsers settings dialog), navigate to the link mentioned above, let the page fully load and tab to another weston desktop, top shows

25% MiniBrowser
14% WebKitWebProcess

where the percentage actually varies from run to run but remains constant when I go "back" to bugzilla (usage drops to 0) and "forth" to the example page within one instance.

[ManDay]

FWIW, here is another example which gives even heavier load (>90%)

http://smartwatch-im-praxistest.de/produkt/casio/casio-wsd-f20-pro-trek/

[Carlos Garcia Campos]

Could this be a dupe of bug #175942? Could you try again with 2.17.92 or trunk?

[Jan-Michael Brummer]

I'm also affected on my tablet + 4k monitor and on pinephone, both running Wayland.

CPU Load on the below test pages:
---------------------------------
4k screen (Wayland) : 100% load
Full-HD (Wayland)   : 45% load

4k + FHD (X)        : 10% load

How can i debug this issue?