[win] Differentiate between fast and non-fast startup path UMAs.
On windows we can complete the ProcessSingleton rendesvouz before we
load chrome.dll and proceed with the rest of chrome startup. If we do it
is known as a fast start. This change adds fast versions of the UMAs
Startup.ShowAppListWarmStart and
Startup.WarmStartTimeFromRemoteProcessStart so we can compare the
timings of the fast and non-fast cases.
Review URL: https://chromiumcodereview.appspot.com/18150005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209914 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/chrome/browser/process_singleton_win.cc b/chrome/browser/process_singleton_win.cc
index cb4a1c3..237004a 100644
--- a/chrome/browser/process_singleton_win.cc
+++ b/chrome/browser/process_singleton_win.cc
@@ -288,7 +288,7 @@
return PROCESS_NONE;
}
- switch (chrome::AttemptToNotifyRunningChrome(remote_window_)) {
+ switch (chrome::AttemptToNotifyRunningChrome(remote_window_, false)) {
case chrome::NOTIFY_SUCCESS:
return PROCESS_NOTIFIED;
case chrome::NOTIFY_FAILED:
