[Bug 111140] Buffer corruption with Chromium on gnome-shell (wayland) after taking a screenshot

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=111140

Jonas Ådahl <jadahl at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jadahl at gmail.com

--- Comment #9 from Jonas Ådahl <jadahl at gmail.com> ---
(In reply to Lionel Landwerlin from comment #8)
> 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 :
> https://www.khronos.org/registry/EGL/extensions/EXT/
> EGL_EXT_image_dma_buf_import.txt
> 
> 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.

Does gl*Tex*Image() here imply glGetTexImage() too then you mean? Does reading
from it mean "manipulate"?

Either way, I created https://gitlab.gnome.org/GNOME/mutter/merge_requests/687
that should avoid reading directly from it. It didn't reproduce with or without
it, so if anyone that can reproduce it can give it a test I'd appreciate it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20190716/e4e72bf9/attachment.html>