<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [SNA HSW] Corruption in OpenGL video output (DRI2 + TearFree)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=95414#c23">Comment # 23</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [SNA HSW] Corruption in OpenGL video output (DRI2 + TearFree)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=95414">bug 95414</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>Sound idiosyncratic of how DRI2 operates in sending new buffers to the client
unsynchonrized to the actual rendering stream of the client (i.e. it is
possible for the buffer to be change in the middle of a draw cycle by sending
an invalidate event after it has done the glClear causing it to refetch the
backbuffer...). Basically (mesa) intel_prepare_render() should only update the
buffers once per frame. Maybe something else but there is a race in DRI2 that
could present with those symptoms.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>