Google Git
Sign in
chromium / chromium / src / cbba6fc07c34cce77555a050ec88eb8a0d9375ef
commitcbba6fc07c34cce77555a050ec88eb8a0d9375ef[log] [tgz]
authorWeizhong Xia <weizhong@google.com>Tue Jun 13 05:46:04 2023
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jun 13 05:46:04 2023
treeeb5cf1f1e3e8b70e072ef4a28763e6b96300f358
parente3cbff8de8bd03d1f0387212bee8e7db7d0635ad [diff]
Do not restart content shell after appending args

In crrev.com/c/4599846 '--enable-threaded-compositing' is sometimes
appended to the command line argument list, which could make two
different VTSs effectively have same set of args.

Sort the command line args and always put '--enable-threaded-
compositing' at the end of the list to handle such scenario.

Removed some duplicated VTSs as they are running with same set of
command line arguments.

Changed the block list to a set from a list. This does not seem to be
a performance issue though. The 'in' operation on the list takes about
10^(-5) seconds previously.

Bug: 770028
Change-Id: I14860ecb34865f0d2e30e644b129022752dd312b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4607540
Reviewed-by: Jonathan Lee <jonathanjlee@google.com>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Weizhong Xia <weizhong@google.com>
Cr-Commit-Position: refs/heads/main@{#1156722}
3 files changed
tree: eb5cf1f1e3e8b70e072ef4a28763e6b96300f358
  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.