Comment # 10
on bug 110721
from alvarex
(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.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
