<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - TearFree breaks when playing back videos in Firefox with GPU accelerated windows enabled in Firefox"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96847#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - TearFree breaks when playing back videos in Firefox with GPU accelerated windows enabled in Firefox"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96847">bug 96847</a>
from <span class="vcard"><a class="email" href="mailto:nw9165-3201@yahoo.com" title="nw9165-3201@yahoo.com">nw9165-3201@yahoo.com</a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=96847#c1">comment #1</a>)
<span class="quote">> Please note that DRI3 overrides TearFree</span >
Funny, I had already asked about this before but nobody replied, see:
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - TearFree"
href="show_bug.cgi?id=37686#c124">https://bugs.freedesktop.org/show_bug.cgi?id=37686#c124</a>.
Also, are you absolutely sure about that?
Because even with:
Option "DRI" "3"
Xorg.0.log says:
[ 16.253] (**) intel(0): TearFree enabled
So it seems like TearFree can be enabled even when DRI3 is enabled.
Also, when enabling DRI3 and leaving TearFree disabled, there's still tearing.
So why should DRI3 override TearFree when DRI3 itself does not provide a tear
free experience?
(In reply to Chris Wilson from <a href="show_bug.cgi?id=96847#c1">comment #1</a>)
<span class="quote">> since the client is given direct
> access to the scanout there is nothing the driver can do (until the client
> relinquishes control of the scanout).</span >
Well, I've also tried it with DRI2 via:
Option "DRI" "2"
but the issue is the same.
(In reply to Chris Wilson from <a href="show_bug.cgi?id=96847#c2">comment #2</a>)
<span class="quote">> first attach Xorg.0.log</span >
Attached:
<a href="https://bugs.freedesktop.org/attachment.cgi?id=124946">https://bugs.freedesktop.org/attachment.cgi?id=124946</a>
(In reply to Chris Wilson from <a href="show_bug.cgi?id=96847#c2">comment #2</a>)
<span class="quote">> double
> check with xf86-video-intel.git. If you can compile with ./configure
> --enable-debug that should help catch the easiest problems (in particular
> losing tracking of DRI3/TearFree switch-over).</span >
Is it really necessary to compile xf86-video-intel with a custom build option
to be able to get a verbose (debug) log? Or what does --enable-debug do?
By the way, if you want to reproduce the issue:
As far as I can tell, the issue is triggered by switching the YouTube video
player to fullscreen.
Regards</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>