Move many ProcessSingleton methods to "protected" visibility as an upcoming refactoring of ProcessS…

chrome/browser/chrome_browser_main.cc

Index: chrome/browser/chrome_browser_main.cc
diff --git a/chrome/browser/chrome_browser_main.cc b/chrome/browser/chrome_browser_main.cc
index 6d1e207be3836482d49f58cc0781ec4f31690ade..f5e408a34a3f2a485992c6b610312bb6424b4d14 100644
--- a/chrome/browser/chrome_browser_main.cc
+++ b/chrome/browser/chrome_browser_main.cc
@@ -1047,9 +1047,13 @@ int ChromeBrowserMainParts::PreMainMessageLoopRunImpl() {
   if (!try_chrome.empty()) {
 #if defined(OS_WIN)
     // Setup.exe has determined that we need to run a retention experiment
-    // and has lauched chrome to show the experiment UI. It is guaranteed that
-    // no other Chrome is currently running as the process singleton was
-    // sucessfully grabbed above.
+    // and has lauched chrome to show the experiment UI.

[robertshield, 2012/11/30 21:52:02]

nit: launched

[gab, 2012/11/30 23:46:15]

This is not actually part of the diff, based off the wrong branch (which
explains the massive bot failures!).

Fixed.

+    if (process_singleton_->FoundOtherProcessWindow()) {
+      // It seems that we don't need to run the experiment since chrome
+      // in the same profile is already running.
+      VLOG(1) << "Retention experiment not required";
+      return TryChromeDialogView::NOT_NOW;
+    }
     int try_chrome_int;
     base::StringToInt(try_chrome, &try_chrome_int);
     TryChromeDialogView::Result answer =