commit | 188e7630e81f47a7dfebcfd69dcc91c8b010e97e | [log] [tgz] |
---|---|---|
author | Liam Brady <lbrady@google.com> | Fri Aug 08 18:13:59 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 08 18:13:59 2025 |
tree | f3c11b30da8dd4fd1ee8da64cf08421fe22b7403 | |
parent | d9b756988cc1c0b348fc0ad2412e4fe1bb341b0c [diff] |
Reland "Add enterprise policy for origin-keyed processes." This is a reland of commit I08e365ec9580356dcd07a61bab0c7d7295dcfa6e The CL was reverted because a bot was failing that turned the feature on. That was treated by my CL as a command-line override, which bypassed site isolation checks that tests were relying on. The intention was to only bypass memory checks if the feature was overridden on, but instead it bypassed all checks to try to simplify logic. The reland will only have it bypass the memory checks, and keep all other checks in place. Original change's description: > Add enterprise policy for origin-keyed processes. > > This CL allows enterprise policy to enable or disable origin-keyed > processes by default. If the policy is explicitly enabled, it will > ignore any memory thresholds or checks on whether site isolation is > enabled. For consistency, this CL also changes command-line overrides to > ignore the same checks. > > Explicitly disabling this policy means that Chrome will not attempt to > enable it (such as for devices over a memory threshold), allowing > enterprises to choose to avoid extra process isolation that might be > enabled by default further down the line. > > The origin-keyed processes enterprise policy can be overridden by the > user if they set the feature flag either in chrome://flags or via > command line arguments. That means that if the enterprise policy wants > OKP by default, the user can choose to disable OKP, and vice versa. > > Change-Id: I08e365ec9580356dcd07a61bab0c7d7295dcfa6e > Bug: 40259221 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6807600 > Reviewed-by: Charlie Reis <creis@chromium.org> > Commit-Queue: Liam Brady <lbrady@google.com> > Reviewed-by: Victor Gabriel Savu <vsavu@google.com> > Cr-Commit-Position: refs/heads/main@{#1498226} Bug: 40259221 Change-Id: Ia3b8febc0acdd800e5e014d0f75d4a7169b165f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6825278 Commit-Queue: Liam Brady <lbrady@google.com> Reviewed-by: Victor Gabriel Savu <vsavu@google.com> Reviewed-by: Charlie Reis <creis@chromium.org> Cr-Commit-Position: refs/heads/main@{#1498923}
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.