wayland: how should dispatch the default wayland display queue?

Daniel Stone daniel at fooishbar.org
Sun Jul 27 13:41:34 PDT 2014


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/3266bebf/attachment.html>


More information about the wayland-devel mailing list