From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108824] Invalid handling when GL buffer is bound on one context and invalidated on another
Date: Thu, 16 May 2019 16:34:43 +0000 [thread overview]
Message-ID: <bug-108824-502-4UKKEXgYsM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108824-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 982 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108824
--- Comment #7 from Baldur Karlsson <baldurk@baldurk.org> ---
I applied the patchset on top of latest mesa
(aa040d3b3c7d068e1ece61c71770c16a54745f89) and I seem to get some rendered
corruption that I don't get with the parent commit before applying the patches.
It seems to only appear in RenderDoc, or at least it doesn't happen when
running tiny demo programs. I can't isolate a simpler test case just now but it
seems reliably reproducible and only shows up when I build with the patches
applied.
To repro with RenderDoc:
* Download or build RenderDoc 1.4
* Build gears3d from https://github.com/gears3d/gears3d
* Launch gears3d through RenderDoc, capture, open the frame
* Step back and forth through the drawcalls and the texture viewer will show up
with some corruption.
Screenshot here: https://i.imgur.com/1Dk7diS.png
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1929 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-16 16:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 20:35 [Bug 108824] Invalid handling when GL buffer is bound on one context and invalidated on another bugzilla-daemon
2019-02-01 15:26 ` bugzilla-daemon
2019-02-01 15:27 ` bugzilla-daemon
2019-03-22 16:56 ` bugzilla-daemon
2019-05-10 5:22 ` bugzilla-daemon
2019-05-13 21:47 ` bugzilla-daemon
2019-05-13 21:53 ` bugzilla-daemon
2019-05-16 16:34 ` bugzilla-daemon [this message]
2019-05-19 23:29 ` bugzilla-daemon
2019-05-20 13:47 ` bugzilla-daemon
2019-05-20 13:48 ` bugzilla-daemon
2019-05-21 8:40 ` bugzilla-daemon
2019-05-21 16:28 ` bugzilla-daemon
2019-05-21 18:35 ` bugzilla-daemon
2019-05-21 20:53 ` bugzilla-daemon
2019-05-22 21:59 ` bugzilla-daemon
2019-09-25 18:29 ` 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-108824-502-4UKKEXgYsM@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox