https://bugzilla.gnome.org/show_bug.cgi?id=761312
--- Comment #2 from Ray Strode [halfline] <rstr...@redhat.com> ---
Created attachment 320042
--> https://bugzilla.gnome.org/attachment.cgi?id=320042&action=edit
wayland: Don't call set_busy twice on the same surface
If the compositor is using a shared memory buffer allocated by
a client, then it's the client's responsibility to refrain from
destroying the buffer until the compositor releases it.
This is accomplished by taking a reference to the cairo surface
assocatiated with the buffer after a frame, and dropping the
reference when the compositor releases the buffer.
In some cases though, the compositor doesn't release the buffer
until a new buffer is set, so if we have staged drawing before
the frame completes we can end up taking multiple references to
the buffer and keeping it alive after it's released.
This commit solves the problem by ensuring we only call
_gdk_wayland_shm_surface_set_busy if isn't already busy.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
