Disarm LockToOrigin for extensions under --isolate-extensions.

chrome/browser/extensions/chrome_content_browser_client_extensions_part.cc

Index: chrome/browser/extensions/chrome_content_browser_client_extensions_part.cc
diff --git a/chrome/browser/extensions/chrome_content_browser_client_extensions_part.cc b/chrome/browser/extensions/chrome_content_browser_client_extensions_part.cc
index 684fbf44ced6e98dce59a7c0b67d434314cf93f4..d83582c070ef195e9731c865263cefff591a1086 100644
--- a/chrome/browser/extensions/chrome_content_browser_client_extensions_part.cc
+++ b/chrome/browser/extensions/chrome_content_browser_client_extensions_part.cc
@@ -218,6 +218,14 @@ bool ChromeContentBrowserClientExtensionsPart::ShouldLockToOrigin(
             .GetExtensionOrAppByURL(effective_site_url);
     if (extension && extension->is_hosted_app())
       return false;
+
+    // http://crbug.com/600441 workaround - Extension process reuse (implemented
+    // above, in ShouldTryToUseExistingProcessHost) means that extension

[Devlin, 2016/04/07 15:06:37]

nit: actually implemented below, right?  Might be worth just saying "implemented
in Should..."

[ncarter (slow), 2016/04/07 21:41:09]

Done.

+    // processes aren't always actually dedicated to a single origin, even in
+    // --isolate-extensions. TODO(nick): Fix this.
+    if (!base::CommandLine::ForCurrentProcess()->HasSwitch(
+            ::switches::kSitePerProcess))
+      return false;
   }
   return true;
 }