Here's the discussion and patch that addressed the issue I was mentioning: https://lists.freedesktop.org/archives/wayland-devel/2017-September/035191.html
On Mon, Mar 12, 2018 at 3:51 PM, Matt Hoosier <matt.hoos...@gmail.com> wrote: > Hi, > > Unless you're using an unreleased version of Weston, I think you're > probably running into a bug that we fixed a few months ago in which > wl_buffer::release() events were prone to sit undispatched in the > server's outgoing queue until some other event happened to need > transmitted. > > -Matt > > On Mon, Mar 12, 2018 at 1:23 PM, Sichem Zhou <sichem...@gmail.com> wrote: >> Hi all, >> >> Dear wayland devs, I have a question regarding to double `wl_buffer` >> management. I don't seem to have wl_buffer released untill some other events >> triggered (for example, the inputs). My current environment is under >> `X11-backend` and a libweston based compositor. >> >> My pipeline follows: (frame, attach, damage, commit) -> buffer switch -> >> wait until one buffer available -> redraw. The `done` event is handled >> differently since it only signals if ready to draw. >> >> Through my experiments, I found out at I wouldn't get either of the >> `release` of `frame done` event if I wasn't using the compositor (moving >> cursor or typing). In this case I guess there is something wrong with my >> pipeline but I couldn't figure out which. I wish to know if there is obvious >> mistakes in my pipeline or the problem lies in the compositor. >> >> Very appreciate any answers. >> >> SZ >> >> >> >> _______________________________________________ >> wayland-devel mailing list >> wayland-devel@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/wayland-devel >> _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
