Google Git
Sign in
chromium / chromium / src / 1f27c0c62eba9be27ddab295a5f230315351aec4
commit1f27c0c62eba9be27ddab295a5f230315351aec4[log] [tgz]
authorJean-Philippe Gravel <jpgravel@chromium.org>Mon Jul 14 14:45:33 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jul 14 14:45:33 2025
tree2da5d173bba34c1d89bf3b6c2e39e1a535e12546
parent11f6c808c46b95084a84ffb665384d3ed942dc7a [diff]
Add a feature param for the default HangWatcher monitoring period

This will allow changing the hang watch monitoring period via a Finch
experiment, if we need to, but it will also allow testing the
HangWatcher in browser tests.

Browser tests would need to shorten the monitoring period, so tests
don't need to wait 10 secondes to observe hangs. Because browser tests
run the HangWatcher in different child processes, the test body can't
directly access these HangWatcher instances. It can however configure
them by setting feature params, which are propagated to all spawned
processes.

Bug: 413314866
Change-Id: Ib00b711a6b90f7be99f768d25e00210c1475c26e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6638519
Reviewed-by: Olivier Li <olivierli@chromium.org>
Commit-Queue: Jean-Philippe Gravel <jpgravel@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1486297}
1 file changed
tree: 2da5d173bba34c1d89bf3b6c2e39e1a535e12546
  1. .github/
  2. agents/
  3. android_webview/
  4. apps/
  5. ash/
  6. base/
  7. build/
  8. build_overrides/
  9. buildtools/
  10. cc/
  11. chrome/
  12. chromecast/
  13. chromeos/
  14. codelabs/
  15. components/
  16. content/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia_web/
  23. gin/
  24. google_apis/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  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. signing_keys
  54. v8
  55. .clang-format
  56. .clang-tidy
  57. .clangd
  58. .cursorignore
  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.