Google Git
Sign in
chromium / chromium / src / 3f93e353f964efad0d13081fee740f355bba57d7
commit3f93e353f964efad0d13081fee740f355bba57d7[log] [tgz]
authorKeren Zhu <kerenzhu@chromium.org>Wed Jun 11 21:12:18 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jun 11 21:12:18 2025
tree565117dedda258ebd617319813015000d871a0ca
parent11d528415b2b4d3dbfe9f48d824a30461a2ab91e [diff]
[M138] preload-topchrome: experimentally reduce number of navigations

The preload candidate selector currently excludes background WebUIs
(i.e. WebUIs that are preloaded and pending to be shown) from preload
candidates. This could cause unnecessary preloading. Consider the
following situation.

- Assuming WebUI A and WebUI B are two preloadable WebUIs.
- At the beginning, WebUI A is preloaded.
- A new preloading is triggered (e.g. BrowserView creation)
- WebUI B is selected to be preloaded.

The preloading of WebUI B is unnecessary. A better strategy is to
preload nothing, because WebUI A is already preloaded and still in the
background.

This CL adds this new preload strategy under feature flag
PreloadTopChromeWebUILessNavigations.

(cherry picked from commit db1c54a539ff208dcc7378da985d29fc4ec7015d)

Bug: 423336929, 424177963
Change-Id: Icd964e25e9fae8472a130c9d01c57a151adccca6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6628833
Reviewed-by: Tom Lukaszewicz <tluk@chromium.org>
Commit-Queue: Keren Zhu <kerenzhu@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1471589}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6638650
Cr-Commit-Position: refs/branch-heads/7204@{#1079}
Cr-Branched-From: d5de512dc9dc8ddfe4e6d71b0637578bb6158683-refs/heads/main@{#1465706}
13 files changed
tree: 565117dedda258ebd617319813015000d871a0ca
  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. .git-blame-ignore-revs
  60. .gitallowed
  61. .gitattributes
  62. .gitignore
  63. .gitmodules
  64. .gn
  65. .mailmap
  66. .rustfmt.toml
  67. .vpython3
  68. .yapfignore
  69. ATL_OWNERS
  70. AUTHORS
  71. BUILD.gn
  72. CODE_OF_CONDUCT.md
  73. codereview.settings
  74. CPPLINT.cfg
  75. CRYPTO_OWNERS
  76. DEPS
  77. DIR_METADATA
  78. LICENSE
  79. LICENSE.chromium_os
  80. OWNERS
  81. PRESUBMIT.py
  82. PRESUBMIT_test.py
  83. PRESUBMIT_test_mocks.py
  84. README.md
  85. SECURITY_OWNERS
  86. 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.