<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Awful screen tearing in a separate X server with DRI3"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97957#c13">Comment # 13</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Awful screen tearing in a separate X server with DRI3"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97957">bug 97957</a>
from <span class="vcard"><a class="email" href="mailto:thellstrom@vmware.com" title="Thomas Hellström <thellstrom@vmware.com>"> <span class="fn">Thomas Hellström</span></a>
</span></b>
<pre>It sounds to me like a back- to back SwapBuffers() is an application bug. The
back buffer content is undefined after a SwapBuffers().
But we shouldn't present a back buffer that's already in the swap chain. Hence
the attached patch.
Also, we should perhaps considering implementing and advertizing
GLX_SWAP_COPY_OML and GLX_SWAP_EXCHANGE_OML on dri3. There seems to be apps
relying on the GLX_SWAP_COPY_OML behavior. Among others glretrace playing back
traces captured on WGL.</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>