Google Git
Sign in
chromium / chromium / src / 0a0924f804ad88a7345597c917f2d53e634668cf
commit0a0924f804ad88a7345597c917f2d53e634668cf[log] [tgz]
authorYan,Shaobo <shaobo.yan@intel.com>Wed Mar 08 07:50:01 2023
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Mar 08 07:50:01 2023
treefddaa5c405c46b0637af10d15a7055619c3d64a4
parent61198914c4319d54e9c8755c05b85300bce52a4b [diff]
Reland "Apply auto expiry mechanism to GPUExternalTexture"

This reland commit ad2a6bfd37ef8a2d8c6eeea447a8ace302fb99cd.

Fix the test case issues.

Original change's description:
> Revert "Apply auto expiry mechanism to GPUExternalTexture"
>
> This reverts commit ad2a6bfd37ef8a2d8c6eeea447a8ace302fb99cd.

> Reason for revert: breaks WebCodecs_GPUExternalTexture_*
> https://luci-milo.appspot.com/ui/p/chromium/builders/ci/Win10%20FYI%20x64%20Release%20(Intel)/956/overview

>> Original change's description:
>> Apply auto expiry mechanism to GPUExternalTexture
>>
>> WebGPU spec updated GPUExternalTexture expire mechanism. It removes
>> GPUExternalTexture.expire and uses auto expiry mechanism.
>>
>> The basic rules are:
>> - ImportExternalTexture should return same object if underly
>>   resource is the same.
>> - GPUExternalTexture should be expire if current task scope finished.
>>   And could be refreshed by importExternalTexture in new task scope.
>>
>> This CL adds auto expiry mechanism and a cache to address these requirements.
>>
>> Bug: chromium:1412338
>> Change-Id: I6ca72d2ea9a013d7729072cb76cb412ecf3a1e86
>> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4258147
>> Commit-Queue: Shaobo Yan <shaobo.yan@intel.com>
>> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
>> Cr-Commit-Position: refs/heads/main@{#1112071}
>
> Bug: chromium:1412338
> Change-Id: I1a9c0b6a2903c6b1e11e2532e4f3ad81081603c8
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4303861
> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
> Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1112220}

Bug:chromium:1412338

Change-Id: Ifb8ee07894880b249559999599dc386170760c98
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4310302
Commit-Queue: Shaobo Yan <shaobo.yan@intel.com>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1114424}
10 files changed
tree: fddaa5c405c46b0637af10d15a7055619c3d64a4
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. 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.