Linux: fix startup race between creating the SingletonLock and listening on SingletonSocket.

BUG=39922
TEST=see bug

Review URL: http://codereview.chromium.org/1612006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@43801 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 3 insertions, 2 deletions

diff --git a/chrome/browser/process_singleton_win.cc b/chrome/browser/process_singleton_win.cc
index 4e8de16..09dec13 100644
--- a/chrome/browser/process_singleton_win.cc
+++ b/chrome/browser/process_singleton_win.cc
@@ -159,10 +159,10 @@ ProcessSingleton::NotifyResult ProcessSingleton::NotifyOtherProcess() {
 // For windows, there is no need to call Create() since the call is made in
 // the constructor but to avoid having more platform specific code in
 // browser_main.cc we tolerate a second call which will do nothing.
-void ProcessSingleton::Create() {
+bool ProcessSingleton::Create() {
   DCHECK(!remote_window_);
   if (window_)
-    return;
+    return true;
 
   HINSTANCE hinst = GetModuleHandle(NULL);
 
@@ -185,6 +185,7 @@ void ProcessSingleton::Create() {
   DCHECK(window_);
 
   win_util::SetWindowUserData(window_, this);
+  return true;
 }
 
 void ProcessSingleton::Cleanup() {