Chrome fails on deqp/functional/gles3/negativeshaderapi.html on nVidia Graphics card |
|||
Issue descriptionWhat steps will reproduce the problem? 1. open chrome with command line: --enable-unsafe-es3-apis 2. Open https://www.khronos.org/registry/webgl/sdk/tests/deqp/functional/gles3/negativeshaderapi.html?webglVersion=2 What is the expected output? What do you see instead? The test should pass in WebGL 2.0 context. But some tests fail. This failure only appears on nVidia graphics card. It can passed on ChromeOS and Linux desktop with Intel graphics card. I guess there are bugs in driver about beginTransformFeedBack.
,
Mar 2 2016
Note that there are some known failures in the es3fTransformFeedbackTests on NVIDIA's drivers which I'm working on suppressing, but I'd be surprised if they're breaking the es3fNegativeShaderApiTests. More likely there's a bug in Chromium's tracking of buffer or transform feedback state.
,
Mar 3 2016
Hi ken, is there a bug tracking the failures your mentioned?
,
Mar 3 2016
Yes -- Issue 526748.
,
Mar 23 2016
I'll take this and look at it once the other transform feedback failures are suppressed.
,
Jun 16 2016
This cannot be reproduced on ToT chromium and WebGL conformance test. Close it now. |
|||
►
Sign in to add a comment |
|||
Comment 1 by yunchao...@intel.com
, Mar 2 2016Labels: GPU-NVidia
Summary: Chrome fails on deqp/functional/gles3/negativeshaderapi.html on nVidia Graphics card (was: Chrome fails on deqp/functional/gles3/negativeshaderapi.html)