diff options
| author | ajwong@chromium.org <ajwong@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-09-14 04:18:30 +0000 |
|---|---|---|
| committer | ajwong@chromium.org <ajwong@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-09-14 04:18:30 +0000 |
| commit | ed6172c83a0215e445f2b4ec83e8f38e2079d135 (patch) | |
| tree | f470cea047b4ee27d18343fae6c53f2497e4a723 /content/worker | |
| parent | fa9ac63a311ff3754dae28f8facc6ffd5db37f5d (diff) | |
| download | chromium_src-ed6172c83a0215e445f2b4ec83e8f38e2079d135.zip chromium_src-ed6172c83a0215e445f2b4ec83e8f38e2079d135.tar.gz chromium_src-ed6172c83a0215e445f2b4ec83e8f38e2079d135.tar.bz2 | |
Remove flags for Workers that violate multiple profile and storage isolation assumptions.
These flags allow the user to have WebWorkers share renderer processes. Unforutnately
this sharing can cause WebWorkers from different Profiles or from different
StoragePartitons to be shared. This violates state isolation boundaries so these
flags just don't work right anyways. Removing.
BUG=144549
Review URL: https://chromiumcodereview.appspot.com/10910207
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@156738 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/worker')
| -rw-r--r-- | content/worker/websharedworkerclient_proxy.cc | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/content/worker/websharedworkerclient_proxy.cc b/content/worker/websharedworkerclient_proxy.cc index dbb8bef..21cd69b 100644 --- a/content/worker/websharedworkerclient_proxy.cc +++ b/content/worker/websharedworkerclient_proxy.cc @@ -192,15 +192,6 @@ bool WebSharedWorkerClientProxy::Send(IPC::Message* message) { } void WebSharedWorkerClientProxy::EnsureWorkerContextTerminates() { - // Avoid a worker doing a while(1) from never exiting. - if (CommandLine::ForCurrentProcess()->HasSwitch( - switches::kWebWorkerShareProcesses)) { - // Can't kill the process since there could be workers from other - // renderer process. - NOTIMPLEMENTED(); - return; - } - // This shuts down the process cleanly from the perspective of the browser // process, and avoids the crashed worker infobar from appearing to the new // page. It's ok to post several of theese, because the first executed task |