Google Git
Sign in
chromium / chromium / src / cfa3d1a940050cc7a624f5d789d3c286373754af
commitcfa3d1a940050cc7a624f5d789d3c286373754af[log] [tgz]
authorKramer Ge <fangzhoug@chromium.org>Wed May 18 20:45:52 2022
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 18 20:45:52 2022
treebd2854c6fd0ad4355652510e7ebb060259ecc545
parent4c94cf16aca9b393557617b960a8653c2e961e4b [diff]
Potential workaround for lacros crash in RemoveDisplay. [merge to M103]

There are a large number of users crashing in RemoveDisplay. The
immediate cause is that exo is sending a wayland message telling Lacros
to remove a display that Lacros does not know about. In general Lacros
should be robust to this. It's unclear if this addresses the underlying
issue of how the lists become out of sync to begin with.

(cherry picked from commit a211f9cb0f72969cd189f0032a484de98542ae51)

Bug: 1299403
Change-Id: I496fd0d4b226f535c980c58a3bba7b02175f1548
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3645243
Reviewed-by: Alexander Dunaev <adunaev@igalia.com>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Kramer Ge <fangzhoug@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1003952}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3653568
Auto-Submit: Alexander Dunaev <adunaev@igalia.com>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Commit-Queue: Robert Kroeger <rjkroege@chromium.org>
Cr-Commit-Position: refs/branch-heads/5060@{#89}
Cr-Branched-From: b83393d0f4038aeaf67f970a024d8101df7348d1-refs/heads/main@{#1002911}
1 file changed
tree: bd2854c6fd0ad4355652510e7ebb060259ecc545
  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/
  22. fuchsia_webengine/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  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. .mailmap
  60. .rustfmt.toml
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.