<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Tahiti+DRI3+Unity+Blender corruption"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97059#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Tahiti+DRI3+Unity+Blender corruption"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97059">bug 97059</a>
from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>I suspect this is a blender bug. It clearly doesn't render at all to the
corrupted parts of its window, but AFAICT it doesn't use any of the
GLX_EXT_buffer_age, GLX_OML_swap_method or GLX_INTEL_swap_event extensions to
find out what if any guarantees there are about the contents of the back buffer
after a buffer swap. blender's assumptions about that may happen to be valid
with DRI2, which can only use up to two buffers, but not with DRI3, which can
use more.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>