Fix login visual hitch on chromebook

chrome/browser/chromeos/login/user_manager_impl.cc

Index: chrome/browser/chromeos/login/user_manager_impl.cc
diff --git a/chrome/browser/chromeos/login/user_manager_impl.cc b/chrome/browser/chromeos/login/user_manager_impl.cc
index 8830cd2a0575247b1c12b91b57db65ce81a761e2..0b72b200789c9731b9d6d9b57d5e3223c6f941a8 100644
--- a/chrome/browser/chromeos/login/user_manager_impl.cc
+++ b/chrome/browser/chromeos/login/user_manager_impl.cc
@@ -189,6 +189,9 @@ UserManagerImpl::~UserManagerImpl() {
     delete *it;
   }
   delete logged_in_user_;
+
+  // Use singleton UserManagerImpl to manage the lifetime of WallpaperManager.
+  delete WallpaperManager::Get();

[Joao da Silva, 2013/01/22 10:04:12]

This is quite strange. Why not make WallpaperManager a Singleton?

(see MediaPlayer::GetInstance() for an example:
chrome/browser/chromeos/media/media_player.cc)

[bshe, 2013/01/22 15:36:26]

Reading comment for singleton here:
http://code.google.com/searchframe#OAMlx_jo-ck/src/base/memory/singleton.h&ex...
I thought it might be good to avoid create singleton as much as possible. And
wallpaper manager can be managed by user manager. But I maybe wrong. I will
convert it to a singleton if you think it doesnt make sense.


On 2013/01/22 10:04:12, Joao da Silva wrote:

 }
 
 void UserManagerImpl::Shutdown() {