Desktop fast shutdown experiment

chrome/browser/chrome_browser_main.cc

Index: chrome/browser/chrome_browser_main.cc
diff --git a/chrome/browser/chrome_browser_main.cc b/chrome/browser/chrome_browser_main.cc
index 3b02122611bd9780277972e204e75b338839e0de..911ccf777f01d7fa011f9025a8ffe721ed96dc34 100644
--- a/chrome/browser/chrome_browser_main.cc
+++ b/chrome/browser/chrome_browser_main.cc
@@ -176,7 +176,9 @@
 #include "chrome/browser/metrics/thread_watcher_android.h"
 #include "ui/base/resource/resource_bundle_android.h"
 #else
+#include "chrome/browser/features.h"
 #include "chrome/browser/feedback/feedback_profile_observer.h"
+#include "chrome/browser/lifetime/application_lifetime.h"
 #endif  // defined(OS_ANDROID)
 
 #if defined(OS_LINUX) && !defined(OS_CHROMEOS)
@@ -1982,6 +1984,10 @@ bool ChromeBrowserMainParts::MainMessageLoopRun(int* result_code) {
       g_browser_process->local_state());
   run_loop.Run();
 
+  if (base::FeatureList::IsEnabled(chrome::kDesktopFastShutdown)) {

[gab, 2016/11/28 16:05:05]

nit: no {} for single line condition/body

[manzagop (departed), 2016/11/29 23:16:05]

Done.

+    chrome::SessionEnding();

[gab, 2016/11/28 16:05:05]

Won't this result in recording the exits in UMA as though they were triggered by
END_SESSION? Do we care?

[manzagop (departed), 2016/11/29 23:16:05]

It will, but I don't think we care in the context of this experiment. We have
Shutdown.ShutdownType, but I don't think it's really looked at or that anything
else sits on top of it.

I'll add rkaplow (from metrics) and hashimoto (the metric owner) to validate.

+  }
+
   return true;
 #endif  // defined(OS_ANDROID)
 }