Bug 100697 - [radeonsi,WebGL] blinking random patches instead of blinking squares
Summary: [radeonsi,WebGL] blinking random patches instead of blinking squares
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/radeonsi (show other bugs)
Version: git
Hardware: Other All
: low minor
Assignee: Default DRI bug account
QA Contact: Default DRI bug account
URL: https://robertsspaceindustries.com/st...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-16 19:32 UTC by Kai
Modified: 2018-08-20 11:54 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Random blinking spots instead of squares (534.18 KB, image/png)
2017-04-16 19:32 UTC, Kai
Details

Description Kai 2017-04-16 19:32:12 UTC
Created attachment 130867 [details]
Random blinking spots instead of squares

When viewing <https://robertsspaceindustries.com/starmap> you can see random blinking patches (see attached screenshot) instead of full screen of blinking squares in the background during the loading screens. The first few seconds of <https://www.youtube.com/watch?v=Xn3MeDnryt8> show how the background should look.
Please note, that the actual star map works fine AFAICT (thus the reduced severity and priority).
This is with the OpenGL stack detailed below and Firefox 52.0.2. Also this doesn't seem to be a duplicate of bug 100036 as that star map seems to render correctly for me with the same setup.

The full stack (Debian testing as a base) is:
GPU: Hawaii PRO [Radeon R9 290] (ChipID = 0x67b1)
Mesa: Git:master/566f2ed571
libdrm: Git:master/c9c77c3717 (tag libdrm-2.4.79)
LLVM: SVN:trunk/r299977 (5.0 devel)
X.Org: 2:1.19.2-1
Linux: 4.10.9
Firmware (firmware-amd-graphics): 20161130-2
libclc: 0.2.0+git20170330-1 (rebuilt for LLVM 5.0)
DDX (xserver-xorg-video-amdgpu): 1.2.0-1+b1

Let me know if you need anything else.
Comment 1 network723 2017-04-16 19:42:33 UTC
While I'm not a dev, but this is very similar to what I see in Xonotic, due to llvm regression, see this bug: https://bugs.freedesktop.org/show_bug.cgi?id=100681

If you can, try building mesa with earlier llvm revision, I myself use 299800 for now.
Comment 2 Kai 2017-04-16 19:47:22 UTC
(In reply to network723 from comment #1)
> While I'm not a dev, but this is very similar to what I see in Xonotic, due
> to llvm regression, see this bug:
> https://bugs.freedesktop.org/show_bug.cgi?id=100681
> 
> If you can, try building mesa with earlier llvm revision, I myself use
> 299800 for now.

Thanks for the pointer but I've seen this issue for quite some time with different versions of Mesa and LLVM. Therefore I do not believe this to be related. I just never got around to report the bug since the main part of the map is rendering fine and the menus are working as well. It's really just the background here.
Comment 3 Timothy Arceri 2018-04-01 00:24:49 UTC
It seems to render incorrectly in Firefox, but renders correctly in Chrome.

The Firefox console has a number of GL_ARB_gpu_shader5 warnings like:

0:2(12): warning: extension `GL_ARB_gpu_shader5' unsupported in fragment shader


For reference it runs fine in both on i965.
Comment 4 Timothy Arceri 2018-04-01 00:26:01 UTC
(In reply to Timothy Arceri from comment #3)
> It seems to render incorrectly in Firefox, but renders correctly in Chrome.

I meant to add that while it renders correctly the performance is really bad in chrome.

> 
> The Firefox console has a number of GL_ARB_gpu_shader5 warnings like:
> 
> 0:2(12): warning: extension `GL_ARB_gpu_shader5' unsupported in fragment
> shader
> 
> 
> For reference it runs fine in both on i965.
Comment 5 Kai 2018-08-20 11:54:19 UTC
Ok, this is fixed now with latest Mesa and LLVM development builds. I'm seeing the squares correctly rendered before Firefox 61 crashes. But since all WebGL-using sites are crashing now (eg. Google Maps), this is very likely something different.

Chromium 68 doesn't crash but still renders incorrectly for me.


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.