Google Git
Sign in
chromium / chromium / src / 37089cfa3de0eb509a0816ee4059196e16fdb553
commit37089cfa3de0eb509a0816ee4059196e16fdb553[log] [tgz]
authorColin Blundell <blundell@chromium.org>Tue May 20 15:44:44 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue May 20 15:44:44 2025
tree84f35839139e96bbb6f9cf97aa3f2472982eb2d7
parent14332f23cab3bc1426e0652de0c5785e8ffae301 [diff]
[//cc] Fix LayerTreeImpl::needs_full_tree_sync_ with TreesInViz

With TreesInViz, there can be multiple pull operations in between remote
display tree updates. Once a pull operation requires a full tree sync,
that bit must stay sticky until the update is actually processed by
VizLayerContext::UpdateDisplayTreeFrom() (which will reset the bit).

Note: With this change, the test in crbug.com/418159586 now fails for a
reason that looks specific to the test in question.

Bug: 418159586
Change-Id: I47ad0e189c5ce269a195edadc91e0b5d2df6c2a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6564470
Commit-Queue: Colin Blundell <blundell@chromium.org>
Reviewed-by: Victor Miura <vmiura@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1462815}
2 files changed
tree: 84f35839139e96bbb6f9cf97aa3f2472982eb2d7
  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. SECURITY_OWNERS
  85. 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.