[Bug 106302] [radeonsi] Garbage content when accessing a texture in multiple shared EGL contexts

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat May 25 20:07:38 UTC 2019


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

--- Comment #2 from seb at vestigecounty.com ---
Pierre-Eric, in my interpretation of OpenGL(R) ES Version 3.0.5 (November 3,
2016) Specification, Appendix 4: Shared Objects and Multiple Contexts, D.3.
Propagating Changes to Objects, Rule 4:...

----
If the contents of an object T are changed in a context other than the current
context, T must be attached or re-attached to at least one binding point in the
current context, or at least one attachment point of a currently bound
container object C, in order to guarantee that the new contents of T are
visible in the current context.

Example: If a texture image is bound to multiple texture bind points and the
texture is changed in another context, re-binding the texture at any one of the
texture bind points is sufficient to cause the changes to be visible at all
texture bind points.
----

...Finish or Fence are not required, since I am re-binding the texture on the
secondary thread where I expect changes to be seen.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20190525/ca8bc803/attachment.html>


More information about the dri-devel mailing list