2014-07-27 22:50 GMT+03:00 Eugen Friedrich <fried...@gmail.com>: > O thanks for the hint about mailing list, > and for clarification on the dispatching logic(I'm not original English > speaker and assume "havok" is like behavior? )
"to break havoc" means creating trouble ;). > > > > 2014-07-27 21:33 GMT+02:00 Giulio Camuffo <giuliocamu...@gmail.com>: > >> FIY, You dropped the mailing list in your reply. >> >> 2014-07-27 22:15 GMT+03:00 Eugen Friedrich <fried...@gmail.com>: >> > The problem is the app never calls wl_display_distpath(_pending) >> > it just creates native handles and then uses EGL for rendering and the >> > events on the main wayland display queue are never dispatched >> > >> > I think if EGL triggers the event(ba calling wl_diplay_sync) it should >> > be >> > also responsible for dispatching >> >> EGL should not dispatch the main queue, that would break havok in the >> apps. What you should do is dispatch the main queue in your app's main >> loop. >> >> > >> > >> > >> > 2014-07-27 20:42 GMT+02:00 Giulio Camuffo <giuliocamu...@gmail.com>: >> > >> >> 2014-07-27 21:14 GMT+03:00 Eugen Friedrich <fried...@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. >> >> >> >> -- >> >> Giulio >> >> >> >> >> >> > >> >> > _______________________________________________ >> >> > wayland-devel mailing list >> >> > wayland-devel@lists.freedesktop.org >> >> > http://lists.freedesktop.org/mailman/listinfo/wayland-devel >> >> > >> > >> > > > _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel