Google Git
Sign in
chromium / chromium / src / cbe0da87e862bc04505d33fc573afc04fa34848a
commitcbe0da87e862bc04505d33fc573afc04fa34848a[log] [tgz]
authorYuwei Huang <[email protected]>Wed Oct 07 21:14:58 2020
committerCommit Bot <[email protected]>Wed Oct 07 21:14:58 2020
treed3708df491ab306a2a7f14cfb951485d48ebe184
parent6b115fbb6040fa8c9950758df6cefb4ee0b6144b [diff]
[remoting host] Install a watchdog during peer connection teardown

This is a simpler approach to tackle (workaround) the blocked network
thread issue when compared to CL 2436278.

This CL simply creates a base::Watchdog that arms before closing the
peer connection, and disarms after the peer connection is closed. If
thread join takes longer than expected then it will crash the host so
that the daemon process can respawn it.

(cherry picked from commit b495e7ee79f9a4d4586a9fb823af2bef6c630e39)

Bug: 1130090
Change-Id: Ib2400e17b848ed07df902a02b344efbf5e15c588
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2446840
Reviewed-by: Lambros Lambrou <[email protected]>
Commit-Queue: Yuwei Huang <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#813937}
TBR: [email protected]
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2458048
Reviewed-by: Yuwei Huang <[email protected]>
Cr-Commit-Position: refs/branch-heads/4280@{#104}
Cr-Branched-From: ea420fb963f9658c9969b6513c56b8f47efa1a2a-refs/heads/master@{#812852}
3 files changed
tree: d3708df491ab306a2a7f14cfb951485d48ebe184
  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. cloud_print/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. jingle/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .vpython
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  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.

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.