wayland: how should dispatch the default wayland display queue?

Giulio Camuffo giuliocamuffo at gmail.com
Sun Jul 27 11:42:35 PDT 2014

2014-07-27 21:14 GMT+03:00 Eugen Friedrich <friedrix at gmail.com>:
> Hi all,
> after debugging a memory consumption issue in simple wayland application i
> found a issue in our wayland graphics backend. Then i took a look into the
> mesa implementation and found the quite similar implementation there.
> 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?

I don't see why the memory consumption should increase. The app should
call wl_display_distpath(_pending) in its main loop, but I'm afraid i
don't quite understand your problem.


> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-devel

More information about the wayland-devel mailing list