0

Enable SubframeProcessReuseThresholds by default with a 512MB threshold.

This feature has been approved to launch with a 512MB threshold, so
enable it by default and remove the corresponding field trial testing
config.

Change-Id: I5e9e6813e22abec293ec9df1b4dff6d6a2486ce5
Bug: 40259123
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6253233
Reviewed-by: Charlie Reis <creis@chromium.org>
Commit-Queue: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1418977}
This commit is contained in:
Alex Moshchuk
2025-02-11 16:09:08 -08:00
committed by Chromium LUCI CQ
parent 7726012bfb
commit 1d3adf8804
2 changed files with 2 additions and 24 deletions
content/public/common
testing/variations

@ -1081,7 +1081,7 @@ BASE_FEATURE(kStrictOriginIsolation,
// much memory is not attempted to be reused.
BASE_FEATURE(kSubframeProcessReuseThresholds,
"SubframeProcessReuseThresholds",
base::FEATURE_DISABLED_BY_DEFAULT);
base::FEATURE_ENABLED_BY_DEFAULT);
// Specifies the memory threshold for the `kSubframeProcessReuseThresholds`
// feature, which only allows a process to be reused for another subframe if the
@ -1091,7 +1091,7 @@ BASE_FEATURE(kSubframeProcessReuseThresholds,
// process reuse experiments.
constexpr base::FeatureParam<double> kSubframeProcessReuseMemoryThreshold{
&kSubframeProcessReuseThresholds, "SubframeProcessReuseMemoryThreshold",
2 * 1024 * 1024 * 1024u};
512 * 1024 * 1024u};
// Disallows window.{alert, prompt, confirm} if triggered inside a subframe that
// is not same origin with the main frame.

@ -22962,28 +22962,6 @@
]
}
],
"SubframeProcessReuseThresholds": [
{
"platforms": [
"android",
"chromeos",
"linux",
"mac",
"windows"
],
"experiments": [
{
"name": "Enabled",
"params": {
"SubframeProcessReuseMemoryThreshold": "2147483648"
},
"enable_features": [
"SubframeProcessReuseThresholds"
]
}
]
}
],
"SunfishFeature": [
{
"platforms": [