New WebContents created via ctrl-click should be in a new process.

chrome/browser/ui/browser_navigator_params.h

Index: chrome/browser/ui/browser_navigator_params.h
diff --git a/chrome/browser/ui/browser_navigator_params.h b/chrome/browser/ui/browser_navigator_params.h
index bf40e6781e709db6d8311cab5e6e07366d3a143d..b7084ad6762992a1874c7e62456947f0b159f34a 100644
--- a/chrome/browser/ui/browser_navigator_params.h
+++ b/chrome/browser/ui/browser_navigator_params.h
@@ -132,6 +132,14 @@ struct NavigateParams {
   // |tabstrip_add_types|.
   WindowOpenDisposition disposition;
 
+  // Controls whether newly created web contents (in case |disposition| asks for
+  // a new tab or window) should attempt to reuse the renderer process of
+  // |source_site_instance|.  For example - new contents created after
+  // ctrl-clicking a link should use always a new renderer, but
+  // chrome.windows.create extensions API should try to keep the new contents in
+  // the same extension process (if same-site).
+  bool use_new_renderer_for_new_contents;
+
   // Sets browser->is_trusted_source. Default is false.
   bool trusted_source;