Created attachment 129040 [details]
They say it is a bug in the mesa drivers and to report it here
Not enough information. We need to know at least:
- what GPU you have. (sudo lspci -s 0:2 -nn)
- what version of Mesa you have. (glxinfo | grep "OpenGL version")
- what kernel version you have. (uname -r)
Please change the status back to REOPENED when you have provided this information.
Additionally, if you are able to capture an apitrace (https://github.com/apitrace/apitrace/blob/master/docs/USAGE.markdown) that reproduces the issue, that would be very helpful.
00:02.0 VGA compatible controller : Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
00:02.1 Display controller : Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07)
OpenGL version string: 2.1 Mesa 13.0.3
Thanks. Can you confirm that if you run the application with INTEL_DEBUG=no16 that the artifacts are not present?
Should that be passed as a kernel param?
Artifacts not present when it is passed as a kernel param however framerate takes a large hit
No, it's an environment variable. If you run the program with "./program" you'd then do "INTEL_DEBUG=no16 ./program"
artifacts not present