dawn_wire: Correctly handle buffer state changes on Destroy() The server didn't take intercept the destroy() call which meant the buffer could be unmapped by dawn_native without the status updated in ServerBuffer. This caused crash when a subsequent UpdateMappedData command was handled and tried to write into the mapped buffer. The client needs to also track destroy() otherwise it could sent an UpdateMappedData to a destroyed buffer which is a fatal error. Tests are added that cover the client-server interaction for this, but the pattern that the following is unfortunately not tested directly against the wire server: - CreateBufferMapped - Destroy - UpdateMappedData Bug: chromium:1068466 Change-Id: If5185d4a8a81cd5f6bb41c9888a18c44c14b2de4 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/18961 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Dawn is an open-source and cross-platform implementation of the work-in-progress WebGPU standard. More precisely it implements webgpu.h that is a one-to-one mapping with the WebGPU IDL. Dawn is meant to be integrated as part of a larger system and is the underlying implementation of WebGPU in Chromium.
Dawn provides several WebGPU building blocks:
webgpu.h version that Dawn implements.webgpu.h.Helpful links:
Developer documentation:
User documentation: (TODO, figure out what overlaps with webgpu.h docs)
(TODO)
Apache 2.0 Public License, please see LICENSE.
This is not an officially supported Google product.