From eb5fae3226fa6d0c542fda54a35e282466167e96 Mon Sep 17 00:00:00 2001 From: Pekka Paalanen Date: Thu, 11 Oct 2012 14:31:11 +0300 Subject: [PATCH] protocol: clarify multiple wl_surface.attach Explicitly say what happens with the wl_buffer.release event, if you attach several wl_buffers without a commit in between. Reported-by: David Herrmann Signed-off-by: Pekka Paalanen --- protocol/wayland.xml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 275ea28d..07fee80e 100644 --- a/protocol/wayland.xml +++ b/protocol/wayland.xml @@ -678,7 +678,9 @@ time after the wl_surface.commit request. When the compositor will not access the pixels anymore, it will send the wl_buffer.release event. Only after receiving wl_buffer.release, the client may re-use - the wl_buffer. + the wl_buffer. A wl_buffer, that has been attached and then replaced + by another attach instead of committed, will not receive a release + event, and is not used by the compositor. Destroying the wl_buffer after wl_buffer.release does not change the surface contents, even if the wl_buffer is still pending for the