RESOLVED FIXED 161904
[GTK] Drop redundant wl_display_flush_clients() call
https://bugs.webkit.org/show_bug.cgi?id=161904
Summary [GTK] Drop redundant wl_display_flush_clients() call
Emanuele Aina
Reported 2016-09-13 04:09:39 PDT
The Wayland GSource::prepare() function already calls wl_display_flush_clients() at every mainloop iteration, so there's no need to further call it on Surface::commit().
Attachments
Patch (3.12 KB, patch)
2016-09-13 04:11 PDT, Emanuele Aina
no flags
Emanuele Aina
Comment 1 2016-09-13 04:11:12 PDT
Carlos Garcia Campos
Comment 2 2016-09-13 05:05:38 PDT
Comment on attachment 288684 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=288684&action=review > Source/WebKit2/ChangeLog:10 > + The Wayland GSource::prepare() function already calls > + wl_display_flush_clients() at every mainloop iteration, so there's no > + need to further call it on Surface::commit(). That's not equivalent, prepare is called before dispatch, and commit happens on dispatch. I'm not saying we need to flush on commit, because I don't know, I copied that from previous patches, but this explanation is not clear to me.
Emanuele Aina
Comment 3 2016-09-13 05:41:56 PDT
Yep, I didn't mean to imply that it was equivalent, just that as far as I can tell, even by asking to Wayland developer around here, there's no reason to call wl_display_flush_clients() in ::commit(), and that the call in ::prepare() is the place where they expected the call to be. For further reference, the Wakefield experimental compositor only does it in the ::prepare() function: https://github.com/alexlarsson/wakefield/blob/master/wakefield-compositor.c#L1919 Let me know how I can make the ChangeLog entry more clear.
WebKit Commit Bot
Comment 4 2016-10-08 16:14:50 PDT
Comment on attachment 288684 [details] Patch Clearing flags on attachment: 288684 Committed r206961: <http://trac.webkit.org/changeset/206961>
WebKit Commit Bot
Comment 5 2016-10-08 16:14:53 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.