Bug 83430

Summary: Document client threading and event queues
Product: Wayland Reporter: Pekka Paalanen <ppaalanen>
Component: waylandAssignee: Wayland bug list <wayland-bugs>
Status: RESOLVED MOVED QA Contact:
Severity: enhancement    
Priority: medium    
Version: unspecified   
Hardware: All   
OS: All   
Whiteboard:
i915 platform: i915 features:
Bug Depends on: 91767    
Bug Blocks: 83429, 91769    

Description Pekka Paalanen 2014-09-03 09:42:29 UTC 
Write a chapter to the "big docs" about client side threading and event queues.

- dispatching a queue from more than one thread is a bad idea; explain why
- therefore, every thread that needs to dispatch should have its own queue
- also every piece of software that needs to dispatch in a controlled context needs its own queue (e.g. libEGL)
- the client API is not multi-thread-dispatch-safe (wl_display_roundtrip)
- a new wl_proxy inherits its factory's queue
- destroying a queue while wl_proxies on it exist is a mistake and may lead to use-after-free when events on that wl_proxy arrive
- wl_display contains the default queue
Comment 1 GitLab Migration User 2018-06-08 23:48:23 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/wayland/wayland/issues/13.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.