<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - graphics corruption on steam client with mesa 19.1.0 rc3 on polaris" href="https://bugs.freedesktop.org/show_bug.cgi?id=110721#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - graphics corruption on steam client with mesa 19.1.0 rc3 on polaris" href="https://bugs.freedesktop.org/show_bug.cgi?id=110721">bug 110721</a> from <a class="email" href="mailto:edisonalvarez@arnet.com.ar" title="alvarex <edisonalvarez@arnet.com.ar>"> alvarex</a> <pre>(In reply to Pierre-Eric Pelloux-Prayer from <a href="show_bug.cgi?id=110721#c9">comment #9</a>) > > (In reply to Ropid from <a href="show_bug.cgi?id=110721#c6">comment #6</a>) > > @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?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>