<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: Don't destroy cursor backing storage when the buffer is released" href="https://bugzilla.gnome.org/show_bug.cgi?id=770952#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: Don't destroy cursor backing storage when the buffer is released" href="https://bugzilla.gnome.org/show_bug.cgi?id=770952">bug 770952</a> from <a href="page.cgi?id=describeuser.html&login=klember%40gnome.org" title="Kalev Lember <klember@gnome.org>"> Kalev Lember</a> <pre>Created <a href="attachment.cgi?id=334911&action=diff" name="attach_334911" title="wayland: Don't destroy cursor backing storage when the buffer is released">attachment 334911</a> <a href="attachment.cgi?id=334911&action=edit" title="wayland: Don't destroy cursor backing storage when the buffer is released">[details]</a> <a href='review?bug=770952&attachment=334911'>[review]</a> wayland: Don't destroy cursor backing storage when the buffer is released As per wayland documentation, a client is free to re-use a buffer and its backing storage after it is released by the compositor. This commit changes the wayland cursor cairo_surface destroy logic so that the surface is destroyed together with the cursor object and kept around meanwhile. This fixes a cairo_surface refcount underrun and a virt-manager crash reported in <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1373372">https://bugzilla.redhat.com/show_bug.cgi?id=1373372</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>