Hmm, maybe it depends on the GPU. It did not reproduce on another desktop PC.
In the Windows 10 (BootCamp) environment on my MacBook Air, the problem occurred about once every two times.
OK) Desktop PC + Windows 10 + Chrome Canary + GeForce GTX 660
NG) MacBook Air + Windows 10(BootCamp) + Chrome Canary + Intel UHD Graphics 617
This pattern is definitely strange. The PG does work for me on Windows.
The problem with WebGPU is that it is still not production ready yet, Chrome does not fully support it nor Babylon (the spec is not completed yet neither), so when there are problems it can be difficult to know the root cause of them…
I know that WebGPU specification development is a long way off. However, I can’t resist trying out new features, and Babylon.js is a progressive effort and I am eager to try out many of them.
BTW, I just wrote an article about using WebGPU in Babylon.js. Sorry, it’s in Japanese.