Track the COOP mismatch in the ProcessAllocationContext The CL tracks whether a process allocation is caused by a COOP mismatch. Currently the browser will fail to reuse the process and allocate a new one when receiving a COOP header in the response under partial site isolation. The CL tracks this reuse failure when creating the site instance after receiving the response header. The failure will be passed to the ProcessAllocationContext when the new site instance tries to allocate a process. Bug: 388998723 Change-Id: Iea2135403ad428393e75c2d2966d3ffcabce8ff6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6238439 Reviewed-by: Rakina Zata Amni <rakina@chromium.org> Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Commit-Queue: Jiacheng Guo <gjc@google.com> Cr-Commit-Position: refs/heads/main@{#1419680}
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.