New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 624272 link

Starred by 1 user
Status: WontFix
Owner:
█ kbr@chromium.org
OOO until 2019-01-24
Closed: Jun 2016
Cc:
█ kbr@chromium.org
piman@chromium.org
█ siev...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Webgl conformance test hangs on Mali T-760 (Samsung Galaxy S6).

Project Member Reported by sohan.jy...@samsung.com, Jun 29 2016 
Version: ToT
OS: Android M

The following webgl conformance test hangs (causes gpu timeout) in Mali T-760 drivers.

https://www.khronos.org/registry/webgl/sdk/tests/conformance/glsl/bugs/temp-expressions-should-not-crash.html

Following is the arm-mali discussion thread,
https://community.arm.com/thread/10127

It hangs in compiling a long shader, while handling the uniform with 10000 operators.

Should we plan to do something here ?

Comment 1 by kbr@chromium.org, Jun 29 2016

Owner: kbr@chromium.org
Status: WontFix (was: Untriaged)
This is a regression test for a previously discovered driver bug. The WebGL conformance tests are, in general, the only line of defense that ensure to WebGL implementations that the underlying graphics drivers have reasonable behavior. In this case the original bug was a stack overflow in one vendor's GLSL compiler.

I'm sorry, but the conformance rules mandate a 100% pass rate. However, depending on the situation, it may not be required to pass on a particular GPU in order to qualify a WebGL implementation as conformant. On the other hand, qualifying a particular device does require all tests to pass on that device. See https://www.khronos.org/registry/webgl/sdk/tests/CONFORMANCE_RULES.txt .

The shader program in question is only being compiled, not even run. If the speed of ARM's GLSL compiler were improved then it should be able to compile the shader.

Chrome passes this test on at least some mobile GPUs so I'm afraid we don't consider this a bug in the browser.

Comment 2 by lafo...@chromium.org, Jun 20 2017

Components: -Internals>GPU>WebGL Blink>WebGL
►

Sign in to add a comment