<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [Bisected]. [Regression]. Wayland. Chromium. Opening on full-screen mode videos lead to flickering white/black squads"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111618#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [Bisected]. [Regression]. Wayland. Chromium. Opening on full-screen mode videos lead to flickering white/black squads"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111618">bug 111618</a>
from <span class="vcard"><a class="email" href="mailto:lionel.g.landwerlin@linux.intel.com" title="Lionel Landwerlin <lionel.g.landwerlin@linux.intel.com>"> <span class="fn">Lionel Landwerlin</span></a>
</span></b>
<pre>That is usually a desynchronization between the compositor and the client
(chromium) of state of the compression of the surface.
One is rendering compressed, the other reading uncompressed. We recently
pointed mutter/gnome-shell to avoid reading the texture of a shared surface
from the CPU (glReadPixels, etc...) because it would trigger that.
We should probably fix the driver, but this is somewhat of a rewrite of how we
deal with aux surfaces.</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>