<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Intel TearFree feature stops working at random"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109618#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Intel TearFree feature stops working at random"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109618">bug 109618</a>
from <span class="vcard"><a class="email" href="mailto:sultan@kerneltoast.com" title="Sultan Alsawaf <sultan@kerneltoast.com>"> <span class="fn">Sultan Alsawaf</span></a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=109618#c7">comment #7</a>)
<span class="quote">> The last flip wasn't reported as a failure -- just to check that corresponds
> with maximising Chromium and tearing? There is a fun bit, in the presence of
> DRI3, it is allowed to take over control of the frontbuffer (because it's
> meant to be flipping) but that does allow clients to render into scanout and
> that might just be the case.
>
> If you recompile xf86-video-intel with --enable-debug=full, there will be a
> lot of information (largely noise) about what the clients are doing and what
> TearFree is up to.</span >
As you suspected, the issue is not present with DRI2; it only occurs with DRI3.</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>