From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106302] [radeonsi] Garbage content when accessing a texture in multiple shared EGL contexts
Date: Wed, 22 May 2019 11:59:02 +0000 [thread overview]
Message-ID: <bug-106302-502-11klPjSC8Y@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106302-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 541 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106302
--- Comment #1 from Pierre-Eric Pelloux-Prayer <pierre-eric@damsy.net> ---
I can reproduce but I don't think it's a bug in Mesa: your createTexture()
function doesn't use any synchronization mechanisms so you can't expect the
other thread/context to pick up the changes mades to the texture.
Adding a call to glFlush or glFinish at the end of createTexture() is enough in
this case to fix the issue.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1408 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-22 11:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 20:06 [Bug 106302] [radeonsi] Garbage content when accessing a texture in multiple shared EGL contexts bugzilla-daemon
2019-05-22 11:59 ` bugzilla-daemon [this message]
2019-05-25 20:07 ` bugzilla-daemon
2019-05-27 18:47 ` bugzilla-daemon
2019-05-28 18:59 ` bugzilla-daemon
2019-05-29 8:00 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-106302-502-11klPjSC8Y@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.