<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Buffer corruption with Chromium on gnome-shell (wayland) after taking a screenshot"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111140#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Buffer corruption with Chromium on gnome-shell (wayland) after taking a screenshot"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111140">bug 111140</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>So looking at the way mutter bind the dmabuf shared with chromium to a 2D
texture, it does so through cogl_egl_texture_2d_new_from_image().
That function seems to rely on GL_OES_EGL_image_external extension :
<a href="https://www.khronos.org/registry/EGL/extensions/EXT/EGL_EXT_image_dma_buf_import.txt">https://www.khronos.org/registry/EGL/extensions/EXT/EGL_EXT_image_dma_buf_import.txt</a>
The extension has this bit in the spec :
There is no support for most of the functions that manipulate
other texture targets (e.g. you cannot use gl*Tex*Image*() functions with
TEXTURE_EXTERNAL_OES).
That makes me think what mutter is doing is illegal.</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>