Google Git
Sign in
dawn / dawn / 33d20bef34be43be79d2e6961e636b074df4aa85
commit33d20bef34be43be79d2e6961e636b074df4aa85[log] [tgz]
authorLokbondo Kung <lokokung@google.com>Tue Jun 10 11:44:08 2025 -0700
committerDawn LUCI CQ <dawn-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jun 10 11:44:08 2025 -0700
tree24b5e3216dbc8dcde1bdc4203d7083ae3cf835c4
parentd64f1fdd35a3fab0a0d46f658fd8ab17a43ac4af [diff]
[dawn][native] Adds a way to fake an error after Device creation.

- This is a follow up to:
  https://dawn-review.googlesource.com/c/dawn/+/245734 where the
  issues in the bugs below should be fixed.
- The fuzz tests linked below were a result of an error happening
  after a Device was successfully allocated, but failed to initialize.
  This is possible in the fuzz tests because we allow Vulkan failure
  fuzzing.
- Updates the device lost event to be updated appropriately when the
  device failed to create. Otherwise, when a device was created but
  initialize failed, the device lost would actually look like the
  device was destroyed. Now only the first |SetLost| on the event
  will be reflected, and hence users will see |FailedCreation|.
- In order to better protect against this, this change adds a way to
  fake a failure in the frontend and adds relevant regression tests.
- Note that as I was making this change, I also filed
  https://github.com/webgpu-native/webgpu-headers/issues/546 upstream
  because of the interaction between RequestDevice and the
  DeviceLostCallback when we have different callback modes for them.

Bug: 421746158, 415350701
Change-Id: I3f2943c66d435b4bbbdca5fbb26c6c2ac388e160
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/245777
Commit-Queue: Brandon Jones <bajones@chromium.org>
Auto-Submit: Loko Kung <lokokung@google.com>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
13 files changed
tree: 24b5e3216dbc8dcde1bdc4203d7083ae3cf835c4
  1. .github/
  2. .vscode/
  3. build_overrides/
  4. docs/
  5. generator/
  6. include/
  7. infra/
  8. scripts/
  9. src/
  10. test/
  11. third_party/
  12. tools/
  13. webgpu-cts/
  14. build
  15. buildtools
  16. testing
  17. .bazelrc
  18. .clang-format
  19. .clang-format-ignore
  20. .clang-tidy
  21. .git-blame-ignore-revs
  22. .gitattributes
  23. .gitignore
  24. .gitmodules
  25. .gn
  26. .style.yapf
  27. .vpython3
  28. AUTHORS
  29. BUILD.bazel
  30. BUILD.gn
  31. CMakeLists.txt
  32. CMakeSettings.json
  33. CODE_OF_CONDUCT.md
  34. codereview.settings
  35. CONTRIBUTING.md
  36. CPPLINT.cfg
  37. DEPS
  38. DIR_METADATA
  39. go.mod
  40. go.sum
  41. go_presubmit_support.py
  42. LICENSE
  43. OWNERS
  44. PRESUBMIT.py
  45. README.chromium
  46. README.md
  47. WATCHLISTS
  48. WORKSPACE.bazel
README.md

Build Status Matrix Space

Dawn, a WebGPU implementation

Dawn is an open-source and cross-platform implementation of the 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 C/C++ headers that applications and other building blocks use.
    • The webgpu.h version that Dawn implements.
    • A C++ wrapper for the webgpu.h.
  • A “native” implementation of WebGPU using platforms' GPU APIs: D3D12, Metal, Vulkan and OpenGL. See per API support for more details.
  • A client-server implementation of WebGPU for applications that are in a sandbox without access to native drivers
  • Tint is a compiler for the WebGPU Shader Language (WGSL) that can be used in standalone to convert shaders from and to WGSL.

Helpful links:

Documentation table of content

Developer documentation:

User documentation: (TODO, figure out what overlaps with the webgpu.h docs)

License

BSD 3-Clause License, please see LICENSE.

Disclaimer

This is not an officially supported Google product.