New issue
Advanced search Search tips

Issue 760778 link

Starred by 6 users
Status: Fixed
Owner:
lukasza@chromium.org
Closed: Oct 2017
Cc:
creis@chromium.org
lukasza@chromium.org
wfh@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Experimenting with full site isolation (--site-per-process) on Canary and Dev channels

Project Member Reported by lukasza@chromium.org, Aug 30 2017 
We plan to run short field trials of --site-per-process mode on Canary and Dev channels, to gather data about its impact on Chrome's process count and resource usage.  Our estimates indicate this mode will likely be too expensive to launch as is, so we are not filing a full launch bug or intending for this to reach Beta or Stable.

The data from the experiment will help us decide on an appropriate policy for how many sites can require dedicated processes.

Experiment doc (internal):
go/site-per-process-experiments
Project Member

Comment 1 by bugdroid1@chromium.org, Sep 1 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/57c772abca620c4b5a6b7691b75b4efa5ef2e1c4

commit 57c772abca620c4b5a6b7691b75b4efa5ef2e1c4
Author: Lukasz Anforowicz <lukasza@chromium.org>
Date: Fri Sep 01 21:15:10 2017

Add feature flag for --site-per-process so that we can run experiments.

This CL introduces a new base::Feature to control whether the full
site isolation (aka --site-per-process) is active.  This CL is
a prerequisite for Canary and Dev experiments with this isolation mode.

I've tested the CL by:
- Running chrome with --enable-features=site-per-process
- Visiting https://csreis.github.io/tests/cross-site-iframe.html
- Going cross-site (complex-page)
- Verifying in Chrome's Task Manager that the subframes are in a
  separate process

Bug:  760778 
Change-Id: I5ac29c8d973b42e76406711895e6a0014616da7e
Reviewed-on: https://chromium-review.googlesource.com/644287
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#499297}
[modify] https://crrev.com/57c772abca620c4b5a6b7691b75b4efa5ef2e1c4/content/common/site_isolation_policy.cc
[modify] https://crrev.com/57c772abca620c4b5a6b7691b75b4efa5ef2e1c4/content/public/common/content_features.cc
[modify] https://crrev.com/57c772abca620c4b5a6b7691b75b4efa5ef2e1c4/content/public/common/content_features.h

Comment 2 by creis@chromium.org, Sep 26 2017

Description: Show this description

Comment 3 by creis@chromium.org, Oct 27 2017

Labels: M-64 OS-Chrome OS-Linux OS-Mac OS-Windows
Owner: lukasza@chromium.org
Status: Fixed (was: Available)
We ran this trial from October 16-23, putting results in the go/site-per-process-experiments doc.  I'll mark it fixed and we can file another bug or re-open if we run another trial.
►

Sign in to add a comment