Google Git
Sign in
chromium / chromium / src / 594de2e7760a0e9f4cc10ef7965e993bdede7338
commit594de2e7760a0e9f4cc10ef7965e993bdede7338[log] [tgz]
authorSaifuddin Hitawala <hitawala@chromium.org>Wed Jun 18 14:14:37 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jun 18 14:14:37 2025
tree73532427be389a6456d0833634cf80898cd03dca
parent7bb5f7ca27db17d5aeb1b4ebb402ace0778935a4 [diff]
Reland "[gpu] Add raster usage dump will be checks in CSI::BeginRasterAccess"

This is a reland of commit 3ac5eded4089acec6287530c9787ac702908d149

Changes from original: Fixed data race as crash key was being written
from 2 different threads and are not thread safe by setting the key
only if usage is not passed in. Tested on linux tsan bot.

Original change's description:
> [gpu] Add raster usage dump will be checks in CSI::BeginRasterAccess
>
> Enforce raster usage over ClientSharedImage::BeginRasterAccess.
>
> Also update client callsites for android, webgpu, paint canvas and
> unittests that were not passing the needed read usage.
>
> Bug: 420632430
> Change-Id: I8430634611fd37b812a5491b200b673f4f3732d9
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6633794
> Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
> Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
> Commit-Queue: Saifuddin Hitawala <hitawala@chromium.org>
> Reviewed-by: Colin Blundell <blundell@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1473749}

Bug: 420632430
Change-Id: Ide1cedaa34dd504c01db5285de447dfa83246942
Include-Ci-Only-Tests: chromium.memory:Linux TSan Tests|content_browsertests
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6646775
Reviewed-by: Colin Blundell <blundell@chromium.org>
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Saifuddin Hitawala <hitawala@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1475563}
7 files changed
tree: 73532427be389a6456d0833634cf80898cd03dca
  1. .github/
  2. android_webview/
  3. apps/
  4. ash/
  5. base/
  6. build/
  7. build_overrides/
  8. buildtools/
  9. cc/
  10. chrome/
  11. chromecast/
  12. chromeos/
  13. codelabs/
  14. components/
  15. content/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. gpu/
  25. headless/
  26. infra/
  27. ios/
  28. ipc/
  29. media/
  30. mojo/
  31. native_client_sdk/
  32. net/
  33. pdf/
  34. ppapi/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. clank
  51. internal
  52. ios_internal
  53. native_client
  54. signing_keys
  55. v8
  56. .clang-format
  57. .clang-tidy
  58. .clangd
  59. .cursorignore
  60. .git-blame-ignore-revs
  61. .gitallowed
  62. .gitattributes
  63. .gitignore
  64. .gitmodules
  65. .gn
  66. .mailmap
  67. .rustfmt.toml
  68. .vpython3
  69. .yapfignore
  70. ATL_OWNERS
  71. AUTHORS
  72. BUILD.gn
  73. CODE_OF_CONDUCT.md
  74. codereview.settings
  75. CPPLINT.cfg
  76. CRYPTO_OWNERS
  77. DEPS
  78. DIR_METADATA
  79. LICENSE
  80. LICENSE.chromium_os
  81. OWNERS
  82. PRESUBMIT.py
  83. PRESUBMIT_test.py
  84. PRESUBMIT_test_mocks.py
  85. README.md
  86. SECURITY_OWNERS
  87. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.