wayland: how should dispatch the default wayland display queue?

[Eugen Friedrich]

Hi Daniel,

thanks, i understood we should add the wl_display_dispatch_pending call in
the application
there is currently no way to avoid this and basically it does not harm.
I only wanted to understand if there is something missing.


2014-07-27 22:41 GMT+02:00 Daniel Stone <daniel at fooishbar.org>:

> Hi Eugen,
>
>
> On Sunday, July 27, 2014, Eugen Friedrich <friedrix at gmail.com> wrote:
>>
>> Our graphics stack creates it's own wayland queue and uses this queue for
>> all wayland objects and only this queue will be dispatched. Our graphics
>> stack calls also wl_display_sync api and the issue is that the wayland
>> library will send a delete event which will go to the default queue of
>> wayland display but this is never dispatched from the driver and the memory
>> consumption increases.
>>
>> So should the graphics stack dispatch also the default queue or should
>> application call somewhere wl_display_dispatch_pending?
>>
>
> The EGL implementation must never dispatch the default queue.
>
> There is a new convenience call in development to fix this, but for now,
> you have to call wl_display_roundtrip, wl_callback_set_queue, and
> wl_callback_add_listener. You can see this used in Mesa.
>
> Hope this helps.
>
> Cheers,
> Daniel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20140727/75cfec68/attachment.html>