Re: wl_buffer is not released for long time.

On Thu, 15 Mar 2018 15:44:18 + Sichem Zhou wrote: > Hi, > > Sorry for the trouble, I forgot to ask that is it safe to call > `wl_display_flush` and `wl_display_dispatch` in different threads? Hi, if you use threads, then you need to be using the prepare_read API of

Re: wl_buffer is not released for long time.

Hi, Sorry for the trouble, I forgot to ask that is it safe to call `wl_display_flush` and `wl_display_dispatch` in different threads? Regards, SZ Le jeu. 15 mars 2018 11 h 17, Sichem Zhou a écrit : > Hi, > > Thanks very much for the patience so far. It's because I didn't

Re: wl_buffer is not released for long time.

Hi, Thanks very much for the patience so far. It's because I didn't do `wl_display_flush` before polling. Regards, SZ Le jeu. 15 mars 2018 04 h 41, Pekka Paalanen a écrit : > On Thu, 15 Mar 2018 00:19:10 + > Sichem Zhou wrote: > > > Dear Pekka, >

Re: wl_buffer is not released for long time.

On Thu, 15 Mar 2018 00:19:10 + Sichem Zhou wrote: > Dear Pekka, > > Thanks for your idea on this, I inserted a callback in the `surface_commit` > function in libweston. From the log I can see that the `surface commit` was > blocked on the server side until some other

Re: wl_buffer is not released for long time.

Dear Pekka, Thanks for your idea on this, I inserted a callback in the `surface_commit` function in libweston. From the log I can see that the `surface commit` was blocked on the server side until some other events happen. On the client side it was clear that I committed two buffers then sleeped

Re: wl_buffer is not released for long time.

On Tue, 13 Mar 2018 14:11:29 + Sichem Zhou wrote: > Dear Matt, > > I just checked my compiled version, indeed I was using a version without > this patch. I patched my local weston but it didn't seem that my problem is > gone. So I guess there could be other problems

Re: wl_buffer is not released for long time.

Dear Matt, I just checked my compiled version, indeed I was using a version without this patch. I patched my local weston but it didn't seem that my problem is gone. So I guess there could be other problems with my code, but thanks for your assistance. Now I can insert the callback in weston to

Re: wl_buffer is not released for long time.

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 wrote: > Hi, > > Unless you're using an unreleased version of Weston,

Re: wl_buffer is not released for long time.

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

wl_buffer is not released for long time.

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: