commit | 510265d5f8d478fa9d2daae372f6a6444216ab27 | [log] [tgz] |
---|---|---|
author | Sebastien Lalancette <seblalancette@chromium.org> | Thu Aug 04 23:13:03 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 04 23:13:03 2022 |
tree | 2091cbca2e029e2d8db65c8236346a235e2669f3 | |
parent | 6e3e949b2846736fb47a9457e984a0488d7888ab [diff] |
[NewEV] Making SystemSignals Service Run Out-of-process on Mac and Linux Before this CL, the SystemSignals service was only running out-of-process on Windows. However, some signals will require loading file and heavier computing, such as going through all pids, on Mac and Linux and, for stability purposes, should be run in a child process. Most of the changes in this CL are about moving files from: //components/device_signals/core/common To //components/device_signals/core/system_signals Since these files should now solely be used in the system_signals child process. The main non-rename changes that are happening are: - //chrome/utility/services.cc - This will now return a service on Mac and Linux as well. - Pulling-up some common (win|mac|linux)system_signals_service into a base_system_signals_service. - Consolidating some BUILD.gn files into one at //chrome/services/system_signals/BUILD.gn Bug: b:231472924 Change-Id: I9a6e7a24875caad91828d73200276b7b81550ce8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3810653 Reviewed-by: Ken Rockot <rockot@google.com> Commit-Queue: Sebastien Lalancette <seblalancette@chromium.org> Reviewed-by: Ted Choc <tedchoc@chromium.org> Reviewed-by: Hamda Mare <hmare@google.com> Cr-Commit-Position: refs/heads/main@{#1031655}
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.