cros: Tighten profile loading

chrome/browser/chromeos/accessibility/accessibility_manager.cc

Index: chrome/browser/chromeos/accessibility/accessibility_manager.cc
diff --git a/chrome/browser/chromeos/accessibility/accessibility_manager.cc b/chrome/browser/chromeos/accessibility/accessibility_manager.cc
index d6d1cc3673319fcca511135cdeb6f28a8df89267..d9a6d312660473e093f5ea5aa05e80e120fa6960 100644
--- a/chrome/browser/chromeos/accessibility/accessibility_manager.cc
+++ b/chrome/browser/chromeos/accessibility/accessibility_manager.cc
@@ -1272,7 +1272,8 @@ void AccessibilityManager::SetProfile(Profile* profile) {
 
 void AccessibilityManager::ActiveUserChanged(
     const user_manager::User* active_user) {
-  SetProfile(ProfileManager::GetActiveUserProfile());
+  if (active_user && active_user->is_profile_created())

[emaxx, 2017/06/19 11:29:11]

Doesn't this change mean that |AccessibilityManager| has now to observe the
profile creation additionally (e.g. as the NOTIFICATION_PROFILE_CREATED event)?

The same question is for similar cases in other files in this CL.

[xiyuan, 2017/06/19 15:28:00]

Not necessarily. |AccessibilityManager|, |MagnificationManagerImpl| and
|SystemClock| observe NOTIFICATION_SESSION_STARTED as well, which is sent after
the user profile has been loaded. The skipped work here would be resumed by
then.

+    SetProfile(ProfileManager::GetActiveUserProfile());
 }
 
 void AccessibilityManager::OnFullscreenStateChanged(bool is_fullscreen,