<html>
<head>
<base href="https://bugzilla.gnome.org/" />
</head>
<body><span class="vcard"><a href="page.cgi?id=describeuser.html&login=jadahl%40gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> <span class="fn">Jonas Ådahl</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - wayland: drawing artifacts as a result of incorrect use of shm_surface busy state"
href="https://bugzilla.gnome.org/show_bug.cgi?id=761733">bug 761733</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>jadahl@gmail.com
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>DUPLICATE
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - wayland: drawing artifacts as a result of incorrect use of shm_surface busy state"
href="https://bugzilla.gnome.org/show_bug.cgi?id=761733#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - wayland: drawing artifacts as a result of incorrect use of shm_surface busy state"
href="https://bugzilla.gnome.org/show_bug.cgi?id=761733">bug 761733</a>
from <span class="vcard"><a href="page.cgi?id=describeuser.html&login=jadahl%40gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> <span class="fn">Jonas Ådahl</span></a>
</span></b>
<pre>Hey. Yes, the buffer reusing was broken (it could also leak buffers), but it
was recently fixed by <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - memory leak"
href="show_bug.cgi?id=761312">bug 761312</a> which got rid of the busy flag completely. A
buffer is now only-reused if a wl_buffer.release is received before painting
the next frame, which should be the common case if the compositor creates a GL
texture from the buffer right after it being committed. In other cases new
buffers are always created and old ones destroyed when released. This could of
course be improved later by keeping track of more buffers, but at least we
should behave correctly now.
So, marking this as a duplicate. Please re-open if you think the issue is still
present.
*** This bug has been marked as a duplicate of <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - memory leak"
href="show_bug.cgi?id=761312">bug 761312</a> ***</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>