RX 480, mesa git, llvm 4.0.0svn_r290385 They have an OpenGL 4.1 and an OpenGL 4.5 backend and it happens on both. Here is a video with the 4.3 backend: https://www.youtube.com/watch?v=VpNFhlzsLHg Here is a (50 megabyte compressed) trace with the 4.5 backend: https://haagch.frickel.club/files/interface.trace.xz Possibly an application bug, but glretrace prints no real errors. If you want to run it yourself, you will need this fix: https://github.com/highfidelity/hifi/pull/9264#issuecomment-268943917
This app looks like totally buggy. Rendering is broken with NVIDIA blob and Nouveau on Maxwell, on SKL and radeonsi. :)
Yup, trace does not even run with AMD blob also... likely does not work anywhere.
I think the correct status should be NOTOURBUG but whatever.
I've reopened, but feel free to close again if it still doesn't work on other drivers. Now that it doesn't hang my GPU anymore I've spent a couple of hours tweaking the source code, available here: https://github.com/ChristophHaag/hifi/commits/master The rendering is better now: The blocky stuff is not green anymore, but it did not disappear. New video showing the problem: https://www.youtube.com/watch?v=pda7cNx3ATE And here is a new trace that runs with an actual 4.5 core context with no mesa GL errors anymore: https://haagch.frickel.club/files/interface-blockartifacts.trace.xz (512 mb uncompressed) If you want to run this trace right now, you need the patch from bug 102308, currently on the list https://lists.freedesktop.org/archives/mesa-dev/2017-August/166827.html
Tried it on nouveau, but I get a ton of Mesa: User error: GL_INVALID_VALUE in glBindBufferRange(offset misaligned 704/256) This is due to the alignment requirements for constant (and texture) buffers being higher on NVIDIA hw than AMD hw.
It doesn't happen anymore on HiFi's RELEASE-7150 tag and radeonsi git, so either of them probably fixed it in the meantime. I'm very happy to close this again.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.