https://bugs.freedesktop.org/show_bug.cgi?id=91750
--- Comment #3 from Yujie Shen <[email protected]> --- (In reply to Jonas Ådahl from comment #2) > Hi and thanks for the report. This seems to be a duplicate of bug 91273, so > closing this one. The problem can be worked around by using the current API > to block dispatching on other threads (see the last paragraph of (omment 2 > of bug 91273 <https://bugs.freedesktop.org/show_bug.cgi?id=91273#c2>. You > will need this until we decide what API we want to introduce fix the issue > properly. > > *** This bug has been marked as a duplicate of bug 91273 *** Thank you. But,this bug is totally different from bug 91273. Bug 91273 reports a bug that 2 threads polling on same display fd in both threads. My bug,namely Bug 91750,reports a bug that a wl_proxy's property is still being modifying in a thread,while another thread may have sent it to server. Please kindly check the attachment"wayland multi-threads interface bug"again. Here is a piece of code to reappear the bug. int main(int argc, char **argv) { .. //sub-thread pthread_t id; pthread_create(&id, NULL, wl_display_roundtrip, &wl_display); ... //main_thread while (1) { ... wl_surface_attach(); window->callback = wl_surface_frame(window->surface); //surface_frame.callback event may have been sent and dispatched by wl_display_roundtrip in sub-thread,before wl_proxy_set_queue in main_thread. wl_proxy_set_queue(window->callback,queue2); wl_callback_add_listener(window->callback, &frame_listener, window); wl_surface_commit(window->surface); } ... return 0; } -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ wayland-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
