FS#50213 - [xorg-server] modesetting DDX causes webkit2gtk windows to be rendered very slowly

Attached to Project: Arch Linux
Opened by Jean-Patrick Guerrero (kilbith) - Sunday, 31 July 2016, 11:56 GMT
Last edited by Jan de Groot (JGC) - Friday, 30 September 2016, 10:47 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Andreas Radke (AndyRTR)
Laurent Carlier (lordheavy)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Example : GNOME Online Account window. There's about 2 seconds of delay between the user's inputting in a field and the text rendering in that window. This is extremely sluggish, whereas it's neat with the Intel DDX.

Additional info:
* xorg-server 1.18.4, i965 GPU (Haswell).

Steps to reproduce:
Just open GNOME Online Account, add e.g. a Google account and see the heavy slowness.
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 30 September 2016, 10:47 GMT
Reason for closing:  Fixed
Additional comments about closing:  webkit2gtk 2.14.0:
"DRI3 is no longer a problem when using the modesetting intel driver."
Comment by Jean-Patrick Guerrero (kilbith) - Sunday, 31 July 2016, 11:57 GMT Comment by Jean-Patrick Guerrero (kilbith) - Sunday, 31 July 2016, 14:04 GMT
Note : Epiphany uses webkit2gtk as well.

Might be related : https://bugs.freedesktop.org/show_bug.cgi?id=85064
Comment by Jan de Groot (JGC) - Monday, 01 August 2016, 05:16 GMT
Isn't this caused by framebuffer compression that is enabled since kernel 4.6? Is it slow with linux-lts also?
Comment by Jean-Patrick Guerrero (kilbith) - Monday, 01 August 2016, 12:22 GMT
Just tested with linux 4.4.16-1-lts and yes, it is as slow as on 4.6.4.
Comment by Laurent Carlier (lordheavy) - Wednesday, 03 August 2016, 05:58 GMT
It should be this upstream bug report:
https://bugs.freedesktop.org/show_bug.cgi?id=85064
Comment by Jean-Patrick Guerrero (kilbith) - Friday, 30 September 2016, 10:44 GMT
This seems fixed with GNOME 3.22, webkit2gtk 2.14.0.

Loading...