Fix chromium-os:10777 and other sync related crashes.

chrome/browser/profiles/profile_impl.cc

Index: chrome/browser/profiles/profile_impl.cc
diff --git a/chrome/browser/profiles/profile_impl.cc b/chrome/browser/profiles/profile_impl.cc
index d4f24d890c29ce168bf401d43e547364158f5b2e..aa727fe8d738c08242ae9d5e2835106f81d6faf2 100644
--- a/chrome/browser/profiles/profile_impl.cc
+++ b/chrome/browser/profiles/profile_impl.cc
@@ -1248,12 +1248,10 @@ TokenService* ProfileImpl::GetTokenService() {
 
 ProfileSyncService* ProfileImpl::GetProfileSyncService() {
 #if defined(OS_CHROMEOS)
-  // If kLoginManager is specified, we shouldn't call this unless login has

[akalin, 2011/01/13 04:15:02]

Hmm.  I'd rather callers explicitly check HasProfileSyncService(), since it
looks like there are only three places in the domui handler that needs that
change.  What do you think?

[stevenjb, 2011/01/13 18:00:49]

Originally I added checks in the settings code, but that does not address issue
10893 (we would need to remove the DCHECK there), and still leaves open the
possibility of other similar bugs, or more subtle ones where sync appears to be
enabled but the backend isn't initialized yet. Granted, these would only show up
for developers not running with kLoginManager, but even so I think it is better
not to set up sync in this place.

That said, I am fine with fixing the settings code and removing the DCHECK for
10893 if you and Tim prefer that.

-  // completed and specified cros_user. Guard with if (HasProfileSyncService())
-  // where this might legitimately get called before login has completed.
-  if (!sync_service_.get() &&
-      CommandLine::ForCurrentProcess()->HasSwitch(switches::kLoginManager)) {
-    LOG(FATAL) << "GetProfileSyncService() called before login complete.";
+  if (!sync_service_.get()) {
+    // In ChromeOS, we only want to initialize sync services explicitly from
+    // the login code. Use HasProfileSyncService() to guard against this.
+    return NULL;
   }
 #endif
   return GetProfileSyncService("");