Commit 2ae381e2 authored by Committed by Nicolas DufresneBrowse files
waylandsink: Avoid race condition on multi-threaded client
When waylandsink is used on some other thread than the main wayland client thread, the waylandsink implementation is vulnerable to a condition related to registry and surface events which handled in seperated event queue. The race that may happen is that after a proxy is created, but before the queue is set, events meant to be emitted via the yet to set queue may already have been queued on the wrong queue. Wayland 1.11 introduced new API that allows creating a proxy wrappper which can help to avoid this race condition.
Showing with 37 additions and 54 deletions