Webgpu dawn crash when calling AdapterGetLimits

[EmilSV]

Summary

When your are using Dawn and calling AdapterGetLimits get an error and crash
Fatal error. System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Steps to reproduce

• Platform: Windows
• API: WebGpu Dawn after commit https://dawn.googlesource.com/dawn/+/f3cac0d4538fe7c738cc4380f47f1cbc32c60324

Comments

I did some investigating and found out that Dawn added a extra field to the WGPULimits sturct called maxBindGroupsPlusVertexBuffers https://dawn.googlesource.com/dawn/+/f3cac0d4538fe7c738cc4380f47f1cbc32c60324

and looks like Wgpu will add it in the future gfx-rs/wgpu#2170 so at this moment they do not have the same size and because of that Dawn will write to protected memory.

[Beyley]

This is probably fixed in master, and on the dev feed, see this page

You should test this with a very recent (if not the latest) build of dawn on master

[EmilSV]

The problem is still on the newest version of silk.net as
https://github.com/dotnet/Silk.NET/blob/main/src/WebGPU/Silk.NET.WebGPU/Structs/Limits.gen.cs
do have the property "MaxBindGroupsPlusVertexBuffers" which the newer version of Dawn uses.

And https://github.com/webgpu-native/webgpu-headers do yet have added "MaxBindGroupsPlusVertexBuffers" to the header file most likely because Wgpu do not have it yet.

[Beyley]

you should open an issue in the webgpu-headers repo about this, since we bind to the standardized headers, theres not much we can do about Dawn ignoring those and breaking ABI compat, for now i would reccomend using wgpu-native instead, as they are always in-sync with at least some version of the standardized headers, and the wgpu-native builds we publish on nuget always match the headers we bind to

[Perksey]

Closing due to this being caused by a non-compliant driver.