Bug 188471 - Tons of rendering artifacts with AC enabled in https://lichess.org
Summary: Tons of rendering artifacts with AC enabled in https://lichess.org
Status: RESOLVED DUPLICATE of bug 188377
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Critical
Assignee: Nobody
URL: https://lichess.org
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-10 08:29 PDT by Sergio Villar Senin
Modified: 2018-08-13 12:51 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sergio Villar Senin 2018-08-10 08:29:21 PDT 
Steps to reproduce:

1- Goto https://lichess.org
2- Move the pointer around, hovering the various UI widgets in the page, also click on some menu (even start a game if you fancy)

Expected outcome:
Good rendering

Actual outcome:
Tons of rendering artifacts, a lot of stuff drawn on places where they should not be

Looked like the typical issue with AC, so I tried WEBKIT_DISABLE_COMPOSITING_MODE=1 and then everything works fine.
Comment 1 Sergio Villar Senin 2018-08-10 08:29:59 PDT 
BTW I'm using the recently released 2.20.4
Comment 2 Michael Catanzaro 2018-08-10 09:19:39 PDT 
If it's a regression from 2.20.3, then please mark this as a duplicate of bug #188377. Carlos Garcia will do a fixup release next week.
Comment 3 Sergio Villar Senin 2018-08-10 09:33:04 PDT 
(In reply to Michael Catanzaro from comment #2)
> If it's a regression from 2.20.3, then please mark this as a duplicate of
> bug #188377. Carlos Garcia will do a fixup release next week.

I don't think it's a regression from 2.20.3 as I've seen it for a while now, like 3-4 months at least. I'll wait for next release and close it if it's really caused by the same change that fixed the other bug.
Comment 4 Michael Catanzaro 2018-08-10 17:27:20 PDT 
No, it's a separate issue, then.
Comment 5 Sergio Villar Senin 2018-08-13 12:51:55 PDT 
It turned out that 2.20.5 fixed this too, so the root cause was the same. Working fine now.

*** This bug has been marked as a duplicate of bug 188377 ***