268071 2024-01-25 03:03:51 -0800 The usage of flat qualifier breaks the WebGL context in Safari 2024-08-30 06:25:53 -0700 1 1 1 Unclassified WebKit WebGL Other iPhone / iPad Unspecified RESOLVED DUPLICATE 272023 InRadar P2 Normal --- 1 endanke webkit-unassigned ahmad.saleem792 dino kbr kkinnunen webkit-bug-importer oldest_to_newest 2007509 0 endanke 2024-01-25 03:03:51 -0800 We have run into a regression regarding the usage of the "flat" storage qualifier in GLSL shaders, which causes the browser to lose the WebGL context across several tabs. This breaks rendering of any further WebGL content and to recover, the browser needs to be force-closed and opened again. The issue was reproducible in Safari on multiple iPad models (MK2K3KN/A and MQDW2TY/A) on one iPhone model (MT9G2ZD/A) and across different iOS versions (16.3.1 and 17.3). On desktop environment we were unable to reproduce it. The exact conditions are not clear, as the browser can render some frames before it loses the context, but usually it happens within a couple of seconds. As a minimal example, we've set the following property in a vertex shader: flat out float v_test; ... v_test = 1.0; And accessed it in the fragment shader similar to: flat in float v_test; ... float alpha = v_test; glFragColor = vec4(1.0, 1.0, 1.0, alpha); The repeated usage of these shaders breaks the context in a couple of seconds. 2007620 1 kkinnunen 2024-01-25 10:55:34 -0800 To confirm: - What does "these shaders breaks the context in a couple of seconds"? Is it WebGL context lost or crash? If I'm reading correctly, it's context lost. If you can share a minimal example, that would be good. In case your flat shading algorithm does not care which vertex provokes the values, please see https://registry.khronos.org/webgl/extensions/WEBGL_provoking_vertex/ to fix your issue. 2007621 2 kkinnunen 2024-01-25 10:55:56 -0800 possibly fix. 2007652 3 endanke 2024-01-25 12:35:48 -0800 It means GL context lost, which we saw in the logs in some cases. In other cases it just manifests by stopping the rendering and turning the target surface to blank, without any additional logs. I'm working on a self-contained example. It turns out just the usage of "flat" is not enough, but it's definitely required to produce the problem. Thanks for the linked example, I'll take a look. 2007792 4 ahmad.saleem792 2024-01-25 18:05:34 -0800 *** This bug has been marked as a duplicate of bug 268070 *** 2007794 5 ahmad.saleem792 2024-01-25 18:06:06 -0800 Apologise! Wanted to mark other way around. 2007796 6 ahmad.saleem792 2024-01-25 18:06:17 -0800 *** Bug 268070 has been marked as a duplicate of this bug. *** 2007836 7 endanke 2024-01-25 21:04:48 -0800 Oh excuse me, apparently I sent the form twice accidentally. Thanks for noticing the duplication. 2009672 8 webkit-bug-importer 2024-02-01 03:04:13 -0800 <rdar://problem/122083140> 2056536 9 kkinnunen 2024-08-30 06:23:21 -0700 Marking this fixed in bug 272023 e38cf95a58 Metal: Release prov. vertex buffers on event set If this persists, please reopen. *** This bug has been marked as a duplicate of bug 272023 *** 2056538 10 kkinnunen 2024-08-30 06:25:53 -0700 iOS 18 beta macOS 15 Beta Sequoia Safari Technology Preview (macOS)