Bug 190249 - [GTK][WPE] Incorrect rendering of layers whose backingStore hasn't changed
Summary: [GTK][WPE] Incorrect rendering of layers whose backingStore hasn't changed
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Miguel Gomez
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-03 07:58 PDT by Miguel Gomez
Modified: 2018-10-04 08:34 PDT (History)
10 users (show)

See Also:


Attachments
Patch (1.82 KB, patch)
2018-10-03 08:03 PDT, Miguel Gomez
no flags Details | Formatted Diff | Diff
Patch (1.80 KB, patch)
2018-10-03 08:09 PDT, Miguel Gomez
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Miguel Gomez 2018-10-03 07:58:42 PDT
CoordinatedGraphicsLayer::flushCompositingStateForThisLayerOnly() sets m_nicosia.performLayerSync to true when the layer properties have changed and the layer needs to be synced. But after that, CoordinatedGraphicsLayer::updateContentBuffers() sets that value to false if the layer has backingStore that doesn't need to me modified. This causes that the layer properties are not synced if the backingStore isn't modified as well.
Comment 1 Miguel Gomez 2018-10-03 08:03:40 PDT
Created attachment 351519 [details]
Patch
Comment 2 Miguel Gomez 2018-10-03 08:09:50 PDT
Created attachment 351520 [details]
Patch
Comment 3 WebKit Commit Bot 2018-10-03 08:48:01 PDT
Comment on attachment 351520 [details]
Patch

Clearing flags on attachment: 351520

Committed r236794: <https://trac.webkit.org/changeset/236794>
Comment 4 WebKit Commit Bot 2018-10-03 08:48:02 PDT
All reviewed patches have been landed.  Closing bug.
Comment 5 Michael Catanzaro 2018-10-04 06:29:51 PDT
Is this the commit that might fix bug #189743?

Should this be added to https://trac.webkit.org/wiki/WebKitGTK/2.22.x for backport to 2.22? The Nicosia code has changed dramatically since branching, so I'm not sure without investigation.
Comment 6 Adrian Perez 2018-10-04 07:28:20 PDT
(In reply to Michael Catanzaro from comment #5)
> Is this the commit that might fix bug #189743?
> 
> Should this be added to https://trac.webkit.org/wiki/WebKitGTK/2.22.x for
> backport to 2.22? The Nicosia code has changed dramatically since branching,
> so I'm not sure without investigation.

Yesterday I was chatting with Žan about this and found it that if we
also merge the patch for bug #188693 beforehand, then this will apply
cleanly on 2.22.x as well. And in that case we also will want the patch
for bug #189224 to avoid hitting a performance regression. Note that I
did *NOT* get to the point of trying to run a build with them applied,
and only checked what would be the minimum needed to get this merged,
in case we wanted.
Comment 7 Michael Catanzaro 2018-10-04 07:42:28 PDT
Is the bug this fixes present on 2.22?
Comment 8 Miguel Gomez 2018-10-04 08:23:07 PDT
In which version is the youtube (In reply to Michael Catanzaro from comment #7)
> Is the bug this fixes present on 2.22?

This fixes a regression that was introduced by the fix to bug #188693, which I think is not in 2.22, so this won't fix anything in that release.
Comment 9 Michael Catanzaro 2018-10-04 08:34:51 PDT
Thanks Miguel. In that case, we surely don't need to backport this.