<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#c15">Comment # 15</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:jadahl@gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> <span class="fn">Jonas Ådahl</span></a>
</span></b>
<pre>(In reply to Lionel Landwerlin from <a href="show_bug.cgi?id=111140#c14">comment #14</a>)
...
<span class="quote">> I could image we could allow glGet*Image* in the driver but that would
> essentially be replicating what you would otherwise do in the application
> (e.g. blit to an offscreen buffer and read that one back).</span >
FWIW, OES_EGL_image_external (used with EGLStreams) has similar limitations.
Other than that, from a Wayland buffer point of view, there are other things
that mandate drawing via an offscreen to get usable output (buffer transforms,
viewports etc), so it's not like there shouldn't be paths in the application
that handles these kind of situations either way.
<span class="quote">>
> The problem is that the driver does a bunch of tracking on what you do with
> the texture and puts it in the most sensible disposition for what it's used.
> Once that goes out of sync with what the other processes have, we're in
> trouble.</span >
I don't think it's worth the trouble to let the driver handle if it would just
complicate things.
<span class="quote">>
> >
> > Either way, I created
> > <a href="https://gitlab.gnome.org/GNOME/mutter/merge_requests/687">https://gitlab.gnome.org/GNOME/mutter/merge_requests/687</a> 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.
>
> That fixes the problem on my side too. Thanks!</span >
Thanks for testing! Thanks to Olivier too :)</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>