From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110721] graphics corruption on steam client with mesa 19.1.0 rc3 on polaris
Date: Wed, 22 May 2019 17:35:26 +0000 [thread overview]
Message-ID: <bug-110721-502-3piUZ70MxO@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110721-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1191 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #10 from alvarex <edisonalvarez@arnet.com.ar> ---
(In reply to Pierre-Eric Pelloux-Prayer from comment #9)
> > (In reply to Ropid from comment #6)
> > @alvarex:
> >
> > Try starting chromium with this command line here, it makes it show
> > corruption everywhere for me here:
> >
> > chromium --ignore-gpu-blacklist --enable-gpu-rasterization
> > --enable-native-gpu-memory-buffers --enable-zero-copy
> > --disable-gpu-driver-bug-workarounds
> >
>
> Same here so I did a bisect.
> There are 2 problematic commits, making the bisect a bit more complicated.
>
> The first one has already been solved by d6053bf2a170.
> The second one is 811fa9a79cf ("mesa: unreference current winsys buffers
> when unbinding winsys buffers").
>
> Using master + this commit reverted: no more corruption in chromium.
for me it doesn't happen on chrome with 64 bits libs, (I couldn't compile
32bits) I tried several versions of chrome, but not that precise one. not sure
if it is the same bug. what version of chrome does steam use?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2222 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 17:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 22:37 [Bug 110721] graphics corruption on steam client with mesa 19.1.0 rc3 on polaris bugzilla-daemon
2019-05-22 2:41 ` bugzilla-daemon
2019-05-22 12:37 ` bugzilla-daemon
2019-05-22 12:40 ` bugzilla-daemon
2019-05-22 13:57 ` bugzilla-daemon
2019-05-22 14:23 ` bugzilla-daemon
2019-05-22 16:07 ` bugzilla-daemon
2019-05-22 16:19 ` bugzilla-daemon
2019-05-22 16:26 ` bugzilla-daemon
2019-05-22 16:31 ` bugzilla-daemon
2019-05-22 16:49 ` bugzilla-daemon
2019-05-22 17:35 ` bugzilla-daemon [this message]
2019-05-22 17:39 ` bugzilla-daemon
2019-05-22 18:59 ` bugzilla-daemon
2019-05-22 19:01 ` bugzilla-daemon
2019-05-22 19:02 ` bugzilla-daemon
2019-05-23 19:02 ` bugzilla-daemon
2019-05-23 19:04 ` bugzilla-daemon
2019-05-23 19:23 ` bugzilla-daemon
2019-05-23 21:38 ` bugzilla-daemon
2019-05-25 7:54 ` bugzilla-daemon
2019-05-25 9:17 ` bugzilla-daemon
2019-05-29 13:35 ` bugzilla-daemon
2019-05-30 16:21 ` bugzilla-daemon
2019-06-18 21:09 ` bugzilla-daemon
2019-06-25 14:55 ` 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-110721-502-3piUZ70MxO@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;
as well as URLs for NNTP newsgroup(s).