Delete desktop/shell instance correctly when chrome is shutting down

chrome/browser/chrome_browser_main_extra_parts_aura.cc

Index: chrome/browser/chrome_browser_main_extra_parts_aura.cc
diff --git a/chrome/browser/chrome_browser_main_extra_parts_aura.cc b/chrome/browser/chrome_browser_main_extra_parts_aura.cc
index 5eab062fcb162a1d947ae222f6ecec1976cf4d07..a69aa71e689b53e0b371bfd6f20154fde230c428 100644
--- a/chrome/browser/chrome_browser_main_extra_parts_aura.cc
+++ b/chrome/browser/chrome_browser_main_extra_parts_aura.cc
@@ -28,3 +28,8 @@ void ChromeBrowserMainExtraPartsAura::PreProfileInit() {
   // Make sure the singleton ScreenOrientationListener object is created.
   ScreenOrientationListener::GetInstance();
 }
+
+void ChromeBrowserMainExtraPartsAura::PostMainMessageLoopRun() {
+  aura_shell::Shell::DeleteInstance();
+  aura::Desktop::DeleteInstance();

[stevenjb, 2011/12/02 01:30:55]

Since aura::Shell::Init() calls aura::Desktop::GetInstance(), shouldn't
aura::Desktop::GetInstance() call aura::Desktop::DeleteInstance()?

[oshima, 2011/12/02 01:45:43]

I assume you mean aura_shell::Shell::DeleteInstance() calls
aura::Desktop::DeleteInstance().
Yes, I thought about it. Technically speaking, desktop instance can outlive
shell instance and
that's the reason why I kept them separated, but I can be convinced either way.
Ben, what do you think?

+}