Google Git
Sign in
chromium / chromium / src / 0d7fb729e2961601214ce0eb6fb46c7c646d3b3d
commit0d7fb729e2961601214ce0eb6fb46c7c646d3b3d[log] [tgz]
authorMichael Tang <tangm@microsoft.com>Mon May 05 23:03:16 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon May 05 23:03:16 2025
tree93767349ec0077f69a574f14aacfc7c8fe9bec31
parent1ee95dec7fdca0a2833bbe0ba5d662a64b3dde3e [diff]
viz: win: Use OverlayLayerId to track lifetime of SwapChainPresenter

Previously we used a list of SwapChainPresenter and implicitly mapped
its order to the order in the overlay list. Now, we use the video layer
ID to own this lifetime. Since the layer ID is now tied to the frame
sink ID, swap chains will remain reused as long as a video element and
source is reused.

This has been manually verified to preserve the swap chain in stream
buffering cases with HLS. It also collects unused video swap chains in
a frame to be reused by new videos in the same frame. This optimizes
the case when a page reuses a video element but switches out the src
with a new video that has the same format and size (a new source
element creates a new layer ID).

Bug: 324460866
Change-Id: Icee50f0b03d58ecf0cc5a1a9e8bd6d0fb8a7991a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6300236
Reviewed-by: Rafael Cintron <rafael.cintron@microsoft.com>
Commit-Queue: Michael Tang <tangm@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1455989}
5 files changed
tree: 93767349ec0077f69a574f14aacfc7c8fe9bec31
  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. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. clank
  50. internal
  51. ios_internal
  52. native_client
  53. signing_keys
  54. v8
  55. .clang-format
  56. .clang-tidy
  57. .clangd
  58. .git-blame-ignore-revs
  59. .gitallowed
  60. .gitattributes
  61. .gitignore
  62. .gitmodules
  63. .gn
  64. .mailmap
  65. .rustfmt.toml
  66. .vpython3
  67. .yapfignore
  68. ATL_OWNERS
  69. AUTHORS
  70. BUILD.gn
  71. CODE_OF_CONDUCT.md
  72. codereview.settings
  73. CPPLINT.cfg
  74. CRYPTO_OWNERS
  75. DEPS
  76. DIR_METADATA
  77. LICENSE
  78. LICENSE.chromium_os
  79. OWNERS
  80. PRESUBMIT.py
  81. PRESUBMIT_test.py
  82. PRESUBMIT_test_mocks.py
  83. README.md
  84. 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.