[Bug 108824] Invalid handling when GL buffer is bound on one context and invalidated on another

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Comment # 10 on bug 108824 from
(In reply to Baldur Karlsson from comment #7)
> 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

I tried to reproduce the issue and actually had 2 different issues:
- before 12bf7cfecf52083c484602f971738475edfe497e: the rendering is corrupted
as described above. Reverting 78e35df52aa2f7d770f929a0866a0faa89c261a9 fixes
the rendering.

- starting from 12bf7cfecf52083c484602f971738475edfe497e: the rendering is
corrupted and wrong: I only see the red gear, the green/blue ones are never
drawn


You are receiving this mail because:
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux