<div dir="ltr">Hi all,<div><br></div><div>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.</div>
<div><br></div><div>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.</div>
<div><br></div><div>So should the graphics stack dispatch also the default queue or should application call somewhere wl_display_dispatch_pending?</div></div>