[Mac] Only create the App Shim Socket after taking process singleton lock.
commitbdad6e651d21f5c8d01700ef537e0e67e52d7163
authorjackhou@chromium.org <jackhou@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Tue, 6 May 2014 08:47:37 +0000 (6 08:47 +0000)
committerjackhou@chromium.org <jackhou@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Tue, 6 May 2014 08:47:37 +0000 (6 08:47 +0000)
tree1138e08262a221c5dda334df8f53cd320dd0a620
parent1a0f7c3eaee2a1dc26b0b82e3b2413b7c98514f9
[Mac] Only create the App Shim Socket after taking process singleton lock.

Previously, Chrome processes initialized AppShimHostManager before taking
the singleton lock. This meant new processes would replace the App Shim
Socket symlink and then delete it as soon as they fail to become the
singleton process.

BUG=168080
TEST= Start Chrome.
Start Chrome again via the command line. I.e. Chromium.app/Contents/MacOS/Chromium
Start an app via its shim. It should work.

Review URL: https://codereview.chromium.org/268903002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@268469 0039d316-1c4b-4281-b951-d872f2087c98
apps/app_shim/app_shim_host_manager_mac.h
apps/app_shim/app_shim_host_manager_mac.mm
chrome/browser/browser_process_platform_part_mac.mm
chrome/browser/chrome_browser_main_mac.h
chrome/browser/chrome_browser_main_mac.mm