<html>
<head>
<base href="https://bugzilla.gnome.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - memory leak"
href="https://bugzilla.gnome.org/show_bug.cgi?id=761312#c19">Comment # 19</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - memory leak"
href="https://bugzilla.gnome.org/show_bug.cgi?id=761312">bug 761312</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>Yes. mesa listens for release events and keeps track of what buffers are in
use. IIRC it'll normally keep 2 or 3 buffers, depending on whether its a
synchronized subsurface or not, in which it needs 3 (active, cached, pending).
Assuming we are not copying the EGL buffer content, in mutter we need to wait
with sending wl_buffer.release until the buffer is replaced by some other on at
least the next commit.
I'm not sure if we'll need to hold the buffer even longer when we have
buffer->plane optimizations.</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>