Multisampled depth renderbuffers of certain widths are corrupted |
||||||||
Issue description[Radar 28901861] On macOS machines with an Intel Haswell GPU, when drawing to an FBO with a multisampled depth renderbuffer attached, some incorrect depth data will be written into the buffer if the buffer width falls into the ranges of [8N+4, 8N+8) where N>=0. This bug causes failures of fbomultisample.*_samples.html’s tests in the WebGL 2.0 conformance suite. This bug does not occur on other GPU types on macOS, nor on other operating systems. Steps to reproduce: 1. Download Chrome Canary and run from the Terminal: /Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --enable-unsafe-es3-apis 2. Check out the KhronosGroup/WebGL repository: git clone https://github.com/KhronosGroup/WebGL.git 3. Launch an HTTP server against that repository: cd WebGL python -m SimpleHTTPServer 4. Navigate the browser to the test cases: http://localhost:8000/sdk/tests/deqp/functional/gles3/fbomultisample.8_samples.html?webglVersion=2&quiet=0 http://localhost:8000/sdk/tests/deqp/functional/gles3/fbomultisample.4_samples.html?webglVersion=2&quiet=0 http://localhost:8000/sdk/tests/deqp/functional/gles3/fbomultisample.2_samples.html?webglVersion=2&quiet=0 These tests are also available online at: http://www.khronos.org/registry/webgl/sdk/tests/deqp/functional/gles3/fbomultisample.8_samples.html?webglVersion=2&quiet=0 http://www.khronos.org/registry/webgl/sdk/tests/deqp/functional/gles3/fbomultisample.4_samples.html?webglVersion=2&quiet=0 http://www.khronos.org/registry/webgl/sdk/tests/deqp/functional/gles3/fbomultisample.2_samples.html?webglVersion=2&quiet=0 Expected Results: Expect all tests to pass, as they do on other operating systems and on other GPU types on macOS. Actual Results: The test cases involving renderbuffers of any depth format fail. OS X Build/Version: macOS Sierra (10.12) MacBook Pro-Mid 2015-Intel Iris Pro Graphics 5200 Notes: NOT reproducible on MacBook-Early 2016-Intel HD Graphics 515
,
Oct 24 2016
,
Apr 8 2017
,
Apr 11 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 11 2018
Has this been fixed in 10.13?
,
Apr 13 2018
Still reproducible. Chrome version Chrome/67.0.3395.0 Operating system Mac OS X 10.13.4 GPU1 VENDOR = 0x8086, DEVICE= 0x0d26 *ACTIVE* Driver version 10.32.48 GL_RENDERER Intel Iris Pro OpenGL Engine
,
Apr 13 2018
Thanks for verifying. That's a bit disappointing. May I assign this to you for tracking?
,
Apr 13 2018
I filed Radar 39402487 about this since I didn't have access to the old Radar 28901861.
,
Apr 13 2018
Also contacted Apple about the new Radar.
,
Apr 13 2018
,
Apr 13 2018
Ken, Jie will track the status of this issue. Actually it is Jie that verified the test on latest Mac OSX, but he used yizhou's account by mistake. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by jie.a.c...@intel.com
, Oct 24 2016