<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - framebuffer from a destroyed drawable is reused when binding the same context to other drawable"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94752#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - framebuffer from a destroyed drawable is reused when binding the same context to other drawable"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94752">bug 94752</a>
from <span class="vcard"><a class="email" href="mailto:gqmelo@gmail.com" title="Guilherme <gqmelo@gmail.com>"> <span class="fn">Guilherme</span></a>
</span></b>
<pre>(In reply to Guilherme from <a href="show_bug.cgi?id=94752#c3">comment #3</a>)
<span class="quote">> Just to add that I could also reproduce the bug with direct rendering. Of
> course, with the patch that forces the second dri_drawable to be allocated
> on the same address of the first one</span >
Ok, I was wrong. With direct rendering the bug cannot happen because the
dri_drawable destruction is postponed and is done only after the second
dri_drawable is created.
But then I raise the question should the fix be done on the Xorg server or
Mesa? As this is an implementation detail I think that the fix should be in
Mesa, probably finding a way to make sure that a dri_drawable will no be freed
before the framebuffer associated to it.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>