RESOLVED INVALID 203947
[GTK] High CPU usage on lichess.org
https://bugs.webkit.org/show_bug.cgi?id=203947
Summary [GTK] High CPU usage on lichess.org
Sergio Villar Senin
Reported 2019-11-07 05:00:02 PST
It's a popular chess server on the internet. The page has a lot of SVG around. It also could run a WebAssembly based version of Stockfish. However I some times left it open for a while an the CPU usage rockets without any kind of user interaction. I'll try to come up with some more data, perhaps a tracing session showcasing the issue.
Attachments
Backtrace (release) (77.12 KB, text/plain)
2020-02-05 10:46 PST, Sergio Villar Senin
no flags
Full backtrace (79.75 KB, text/plain)
2020-07-10 05:53 PDT, Alberto Garcia
no flags
Sergio Villar Senin
Comment 1 2020-02-05 10:46:57 PST
Created attachment 389829 [details] Backtrace (release) Not very good because it's from Debian's package but I'm having a hard time reproducing it with trunk
Sergio Villar Senin
Comment 2 2020-02-06 07:11:15 PST
I'm starting to suspect that this is caused by the memory pressure handler. I'm running trunk in console and I noticed that there was the following output Memory pressure relief: Total: res = 16994304/17072128/77824, res+swap = 9715712/9715712/0 Memory pressure relief: Total: res = 379883520/376602624/-3280896, res+swap = 376217600/376217600/0 I've tons of free memory ATM (>10Gb), so we might be falling into some trap, forcing us to enter a never ending loop of memory reliefs...
Sergio Villar Senin
Comment 3 2020-02-06 07:17:08 PST
(In reply to Sergio Villar Senin from comment #2) > I'm starting to suspect that this is caused by the memory pressure handler. > I'm running trunk in console and I noticed that there was the following > output > > Memory pressure relief: Total: res = 16994304/17072128/77824, res+swap = > 9715712/9715712/0 > Memory pressure relief: Total: res = 379883520/376602624/-3280896, res+swap > = 376217600/376217600/0 > > I've tons of free memory ATM (>10Gb), so we might be falling into some trap, > forcing us to enter a never ending loop of memory reliefs... Ooops I was getting the error but it was caused by another instance running debian's webkitgtk, so forget about this comment.
Sergio Villar Senin
Comment 4 2020-04-23 07:46:54 PDT
Might be caused by https://bugs.webkit.org/show_bug.cgi?id=210561. I'll keep an eye on it.
Alberto Garcia
Comment 5 2020-07-09 03:24:41 PDT
I'm also having this problem with WebKitGTK 2.28.3
Alberto Garcia
Comment 6 2020-07-10 05:53:29 PDT
Created attachment 403961 [details] Full backtrace Here's a full backtrace taken with WebKitGTK 2.28.3 in Debian buster. This is release build but without optimizations and full debugging symbols.
Carlos Garcia Campos
Comment 7 2020-07-10 06:48:51 PDT
(In reply to Alberto Garcia from comment #6) > Created attachment 403961 [details] > Full backtrace > > Here's a full backtrace taken with WebKitGTK 2.28.3 in Debian buster. > > This is release build but without optimizations and full debugging symbols. The bt shows that the AC mode is forced disabled, so this is somehow expected, it's using the CPU for which the GPU is expected to be used for. I think this is because ephy has AC mode disabled in debian stable.
Alberto Garcia
Comment 8 2020-07-10 06:58:42 PDT
I confirm that org.gnome.Epiphany.web hardware-acceleration-policy was set to 'never' (the default value). Changing it to 'on-demand' solves the problem.
Note You need to log in before you can comment on or make changes to this bug.