chromium/src
0
Fork 0
Code Activity

Docs: Include fenced frames in "Aggressive Reuse" section

Browse Source 
Change-Id: I41fbe4107de5169e7093b28c127bb8b02bdc86b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3727307
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1024713}
This commit is contained in:
Adithya Srinivasan
2022-07-15 13:27:28 +00:00
committed by Chromium LUCI CQ
parent a1be8d6449
commit c8e3d599cf
1 changed files with 9 additions and 7 deletions

16
docs/process_model_and_site_isolation.md

@ -322,13 +322,15 @@ decision.
limit, and instead relies on the OS to discard processes.
* **Aggressive Reuse**: For some cases (including on Android), Chromium will
aggressively look for existing same-site processes to reuse even before
reaching the process limit. Out-of-process iframes (OOPIFs) use this
approach, such that an `example.com` iframe in a cross-site page will be
placed in an existing `example.com` process (in any browsing context group),
even if the process limit has not been reached. This keeps the process
count lower, based on the assumption that most iframes are less resource
demanding than top-level documents. Similarly, ServiceWorkers are generally
placed in the same process as a document that is likely to rely on them.
reaching the process limit. Out-of-process iframes (OOPIFs) and [fenced
frames](https://developer.chrome.com/en/docs/privacy-sandbox/fenced-frame/)
use this approach, such that an `example.com` iframe in a cross-site page
will be placed in an existing `example.com` process (in any browsing context
group), even if the process limit has not been reached. This keeps the
process count lower, based on the assumption that most iframes/fenced frames
are less resource demanding than top-level documents. Similarly,
ServiceWorkers are generally placed in the same process as a document that
is likely to rely on them.
* **Extensions**: Chromium ensures that extensions do not share a process with
each other or with web pages, but also that a large number of extensions
will not consume the entire soft process limit, forcing same-site web pages