Bug 238197 - WebGL: rendering difference OpenGL, Metal: MSAA + disable depth_test causes depth invalid depth buffer (AMD)
Summary: WebGL: rendering difference OpenGL, Metal: MSAA + disable depth_test causes d...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebGL (show other bugs)
Version: WebKit Local Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2022-03-22 02:32 PDT by Kimmo Kinnunen
Modified: 2022-03-29 02:33 PDT (History)
8 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kimmo Kinnunen 2022-03-22 02:32:50 PDT 
WebGL: rendering difference OpenGL, Metal, AMD: MSAA + disable depth_test causes depth invalid depth buffer

iMacPro1,1 AMD OpenGL: white outer rectangle
iMacPro1,1 AMD Metal: black outer rectangle

https://github.com/brendan-duncan/webgl_bug_tests/blob/main/msaa_depth_buffer.html
and viewed from here:
https://brendan-duncan.github.io/webgl_bug_tests/msaa_depth_buffer.html

From bug 238118
Comment 1 Kenneth Russell 2022-03-22 12:19:31 PDT 
What's the behavior on Chrome Canary, both with the defaults, and with the command line argument:
  --use-angle=metal
? If the two paths render identically there, then this will be fixed with the forthcoming ANGLE roll in Bug 238171.

On my 2017 dual-GPU Intel/AMD MacBook Pro, I don't see a behavioral difference in either Canary or stable Safari 15.4, using gSwitch to force on the AMD GPU. This might be specific to this particular GPU family. There have certainly been other bugs specific to newer AMD GPUs than were in the 2017 MBP.
Comment 2 Radar WebKit Bug Importer 2022-03-29 02:33:16 PDT 
<rdar://problem/90972518>