UserManager shutdown now also stops the profile image downloader.

chrome/browser/chromeos/chrome_browser_main_chromeos.cc

Index: chrome/browser/chromeos/chrome_browser_main_chromeos.cc
diff --git a/chrome/browser/chromeos/chrome_browser_main_chromeos.cc b/chrome/browser/chromeos/chrome_browser_main_chromeos.cc
index 08261d234e910cdc248185030d4978b4cc1b30cb..53f45031247ebf41edcda96900004ca48144199c 100644
--- a/chrome/browser/chromeos/chrome_browser_main_chromeos.cc
+++ b/chrome/browser/chromeos/chrome_browser_main_chromeos.cc
@@ -769,7 +769,9 @@ void ChromeBrowserMainPartsChromeos::PostMainMessageLoopRun() {
   AccessibilityManager::Shutdown();
 
   // Let the UserManager and WallpaperManager unregister itself as an observer
-  // of the CrosSettings singleton before it is destroyed.
+  // of the CrosSettings singleton before it is destroyed. This also ensures
+  // that the UserManager has no URLRequest pending (see
+  // http://crbug.com/276659).
   UserManager::Get()->Shutdown();
   WallpaperManager::Get()->Shutdown();
 
@@ -780,12 +782,13 @@ void ChromeBrowserMainPartsChromeos::PostMainMessageLoopRun() {
   // Clean up dependency on CrosSettings and stop pending data fetches.
   KioskAppManager::Shutdown();
 
+  // We first call PostMainMessageLoopRun and then destroy UserManager, because
+  // Ash needs to be closed before UserManager is destroyed. Also, on some tests
+  // MergeSessionThrottle::ShouldShowMergeSessionPage gets triggered during
+  // PostMainMessageLoopRun, which also requires UserManager to live (see
+  // http://crbug.com/243364).
   ChromeBrowserMainPartsLinux::PostMainMessageLoopRun();
 
-  // Destroy the UserManager after ash has been destroyed and
-  // ChromeBrowserMainPartsLinux::PostMainMessageLoopRun run.  The latter might
-  // trigger MergeSessionThrottle::ShouldShowMergeSessionPage, which requires
-  // the UserManager to exist.
   UserManager::Destroy();
 }