diff options
| author | Simon Ser <contact@emersion.fr> | 2021-05-26 12:07:17 +0200 |
|---|---|---|
| committer | Simon Ser <contact@emersion.fr> | 2021-06-11 14:05:27 +0000 |
| commit | 3e897faa29d13bef6f9af31d4f2e89a526e60f4c (patch) | |
| tree | 93e1d89eb6f99d4b9d80761d1f93e993b0380a8b /src | |
| parent | shm: remove wl_shm_buffer.pool NULL checks (diff) | |
| download | wayland-3e897faa29d13bef6f9af31d4f2e89a526e60f4c.tar wayland-3e897faa29d13bef6f9af31d4f2e89a526e60f4c.tar.gz wayland-3e897faa29d13bef6f9af31d4f2e89a526e60f4c.tar.bz2 wayland-3e897faa29d13bef6f9af31d4f2e89a526e60f4c.tar.lz wayland-3e897faa29d13bef6f9af31d4f2e89a526e60f4c.tar.xz wayland-3e897faa29d13bef6f9af31d4f2e89a526e60f4c.tar.zst wayland-3e897faa29d13bef6f9af31d4f2e89a526e60f4c.zip | |
protocol: allow immediate wl_buffer.destroy if not re-used
Allow wl_buffer objects to be destroyed without having to wait for
wl_buffer.release if the underlying storage isn't going to be
re-used.
The main motivation for this is to avoid glitches when a client is
torn down. When a client disconnects, all of its objects are destroyed
in arbitrary order. However some compositors will still need to
access the destroyed buffer's underlying storage afterwards, e.g. for
visual effects (fade-out) or for atomic layout updates (wait for other
clients to commit a new buffer before hiding the buffer).
It's still incorrect for clients to destroy a wl_buffer and mutate
the underlying storage without waiting for wl_buffer.release.
Signed-off-by: Simon Ser <contact@emersion.fr>
Closes: https://gitlab.freedesktop.org/wayland/wayland/-/issues/185
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions