Bug 282982

Summary: Our game renders only black pixels now that WebGPU is enabled by default
Product: WebKit Reporter: Jesper van den Ende <jespertheend>
Component: WebGPUAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ik, mwyrzykowski, tzagallo, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Safari Technology Preview   
Hardware: Mac (Apple Silicon)   
OS: macOS 14   
Attachments:
Description Flags
Looks like this is working on WebKit main, let me see which change resolved it none

Jesper van den Ende
Reported 2024-11-12 04:41:09 PST
Our game uses a WebGPU renderer in supported browsers: https://pelicanparty.games/mouse In Chrome and Firefox this works, but in Safari the entire screen is black. It's difficult for me to debug what's going on because nothing is being logged to the console either. You can force the use of the older webgl renderer by adding '&renderer=webgl' to the end of the url inside the iframe: https://4e416f7e-b92d-4439-9460-f599440a677d.pelicontent.com/latest#game=mouse&renderer=webgl
Attachments
Looks like this is working on WebKit main, let me see which change resolved it (534.35 KB, image/png)
2024-11-12 08:34 PST, Mike Wyrzykowski 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Jesper van den Ende
Comment 1 2024-11-12 05:31:51 PST
Fwiw I'm also seeing this same issue on the public beta of iOS 18.2 (22C5125e)
Radar WebKit Bug Importer
Comment 2 2024-11-12 08:18:41 PST
<rdar://problem/139723212>
Mike Wyrzykowski
Comment 3 2024-11-12 08:27:54 PST
WebKit thinks GPUCommandEncoder.beginComputePass() is being called prior to .end() on the previous pass, leading to a validation error.
Mike Wyrzykowski
Comment 4 2024-11-12 08:30:02 PST
Regarding debugging, you can use push/popErrorScope to see "encoder state is locked" being emitted - https://www.w3.org/TR/webgpu/#dom-gpudevice-pusherrorscope
Mike Wyrzykowski
Comment 5 2024-11-12 08:34:14 PST
Created attachment 473208 [details] Looks like this is working on WebKit main, let me see which change resolved it
Mike Wyrzykowski
Comment 6 2024-11-12 08:35:52 PST
Indeed it is working for me as of 286382@main
Mike Wyrzykowski
Comment 7 2024-11-12 09:13:07 PST
This is resolved by https://commits.webkit.org/286121@main which should land in Safari Technology Preview 208 or 209 most likely. *** This bug has been marked as a duplicate of bug 279373 ***
Note You need to log in before you can comment on or make changes to this bug.