Make AppShimHostManager a RefCountedThreadSafe.

apps/app_shim/app_shim_host_manager_mac.mm

Index: apps/app_shim/app_shim_host_manager_mac.mm
diff --git a/apps/app_shim/app_shim_host_manager_mac.mm b/apps/app_shim/app_shim_host_manager_mac.mm
index 049ba5b4fea07c95f2aa1be57c92da73f51bd18c..c364c1a6a05a366da293be71e9b1416f106d5908 100644
--- a/apps/app_shim/app_shim_host_manager_mac.mm
+++ b/apps/app_shim/app_shim_host_manager_mac.mm
@@ -31,8 +31,7 @@ AppShimHostManager::AppShimHostManager() {
   apps::AppShimHandler::SetDefaultHandler(&extension_app_shim_handler_);
   BrowserThread::PostTask(

[tapted, 2013/09/09 21:48:36]

Ah, so since reference counts start from zero, this needs to be done after the
newly constructed object is assigned to the app_shim_host_manager_ member of
BrowserProcessPlatformPart. Some options are to make InitOnFileThread public, or
make a new Init() member function for
BrowserProcessPlatformPart::PreMainMessageLoopRun to call.

I'd probably go with essentially renaming this function to Init() and having a
constructor with an empty body. The empty constructor will still call default
initializers for data members, but I don't think we need to worry about
separating out the Init steps in ExtensionAppShimHandler() - the interesting
initialization there already waits for profile creation.

       BrowserThread::FILE, FROM_HERE,
-      base::Bind(&AppShimHostManager::InitOnFileThread,
-          base::Unretained(this)));
+      base::Bind(&AppShimHostManager::InitOnFileThread, this));
 }
 
 AppShimHostManager::~AppShimHostManager() {
@@ -52,8 +51,7 @@ void AppShimHostManager::InitOnFileThread() {
   factory_.reset(new IPC::ChannelFactory(socket_path, this));
   BrowserThread::PostTask(
       BrowserThread::IO, FROM_HERE,
-      base::Bind(&AppShimHostManager::ListenOnIOThread,
-          base::Unretained(this)));
+      base::Bind(&AppShimHostManager::ListenOnIOThread, this));
 }
 
 void AppShimHostManager::ListenOnIOThread() {