fix: disable kSpareRendererForSitePerProcess feature
This commit is contained in:
parent
9d72bd4de4
commit
28cff4644e
1 changed files with 6 additions and 0 deletions
|
@ -211,6 +211,12 @@ void AtomBrowserMainParts::InitializeFeatureList() {
|
|||
// Chromium drops support for the old sandbox implmentation.
|
||||
disable_features += std::string(",") + features::kMacV2Sandbox.name;
|
||||
#endif
|
||||
// Disable creation of spare renderer process with site-per-process mode,
|
||||
// it interferes with our process preference tracking for non sandboxed mode.
|
||||
// Can be reenabled when our site instance policy is aligned with chromium
|
||||
// when node integration is enabled.
|
||||
disable_features +=
|
||||
std::string(",") + features::kSpareRendererForSitePerProcess.name;
|
||||
auto feature_list = std::make_unique<base::FeatureList>();
|
||||
feature_list->InitializeFromCommandLine(enable_features, disable_features);
|
||||
base::FeatureList::SetInstance(std::move(feature_list));
|
||||
|
|
Loading…
Reference in a new issue