<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Setting a queue on a wl_proxy is racy if some other thread is dispatching the default queue" href="https://bugs.freedesktop.org/show_bug.cgi?id=91273#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Setting a queue on a wl_proxy is racy if some other thread is dispatching the default queue" href="https://bugs.freedesktop.org/show_bug.cgi?id=91273">bug 91273</a> from <a class="email" href="mailto:boram1288@gmail.com" title="Boram <boram1288@gmail.com>"> Boram</a> <pre>> All threads call wl_display_read_events() after returning from poll(), but > only the last thread reads the data from the fd. That way we make sure all > threads who called wl_display_prepare_read_queue() will come out of poll > before we read the data. In multi-thread application, looks we need to avoid to use dispatch()/dipatch_queue(). And there might be no problem if every threads call prepare_read(), poll() and read_events(). For toolkits to support multi-thread, they also need to be fixed to use prepare_read/read_events, as well as mesa Pekka Paalanen mentioned above. To replace roundtrip()/dispatch()/dispatch_queue(), can wayland offer a new convenient API which internally calls poll() and read_events()? i.e, wl_display_poll_read()? It will be more convenient than calling poll() and read_events() directly by each library.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>