Implement install module verification metric.

chrome/browser/chrome_browser_main_win.cc

Index: chrome/browser/chrome_browser_main_win.cc
diff --git a/chrome/browser/chrome_browser_main_win.cc b/chrome/browser/chrome_browser_main_win.cc
index 16a64525c3436361ae119b913d4ea76e257f8623..9150caf7d8fa1634aae01e9479a19c6050da4f05 100644
--- a/chrome/browser/chrome_browser_main_win.cc
+++ b/chrome/browser/chrome_browser_main_win.cc
@@ -22,6 +22,7 @@
 #include "base/win/windows_version.h"
 #include "base/win/wrapped_window_proc.h"
 #include "chrome/browser/browser_util_win.h"
+#include "chrome/browser/install_module_verifier_win.h"
 #include "chrome/browser/profiles/profile_info_cache.h"
 #include "chrome/browser/profiles/profile_shortcut_manager.h"
 #include "chrome/browser/shell_integration.h"
@@ -38,6 +39,7 @@
 #include "chrome/installer/util/install_util.h"
 #include "chrome/installer/util/l10n_string_util.h"
 #include "chrome/installer/util/shell_util.h"
+#include "content/public/browser/browser_thread.h"
 #include "content/public/common/main_function_params.h"
 #include "grit/app_locale_settings.h"
 #include "grit/chromium_strings.h"
@@ -224,6 +226,16 @@ void ChromeBrowserMainPartsWin::ShowMissingLocaleMessageBox() {
                  MB_OK | MB_ICONERROR | MB_TOPMOST);
 }
 
+void ChromeBrowserMainPartsWin::PostBrowserStart() {
+  ChromeBrowserMainParts::PostBrowserStart();
+
+  content::BrowserThread::GetMessageLoopProxyForThread(

[sky, 2013/09/24 20:16:16]

Why do we need to delay here? Assuming we do, document why and why 45 seconds.

[Finnur, 2013/09/25 12:54:22]

I touched on this in my earlier comment. In short: When I was (in another
changelist, see https://codereview.chromium.org/15969017/) making the Module
Enumerator run automatically on XP there were concerns that it would interfere
with startup. Carlos listed (in that changelist) a number of things that start
at various intervals and said (paraphrasing) "judging by what else is starting
up (and at which time) it looks like 45 seconds is a good slot to run this
potentially lengthy operation at" (can take several seconds in worst cases).
Since this changelist would (without the delay) reverse that decision (trigger
the ModuleEnumerator to run sooner), we applied the same logic here.

On 2013/09/24 20:16:16, sky wrote:

[erikwright (departed), 2013/09/25 19:58:08]

See Finnur's comment in this CL, which references this prior comment from cpu:

https://codereview.chromium.org/15969017/#msg6

I would love to have less arbitrary ways to do this kind of deferral but I
believe this is the state of the art for now.

+      content::BrowserThread::UI)->PostDelayedTask(
+          FROM_HERE,
+          base::Bind(&BeginModuleVerification),
+          base::TimeDelta::FromSeconds(45));
+}
+
 // static
 void ChromeBrowserMainPartsWin::PrepareRestartOnCrashEnviroment(
     const CommandLine& parsed_command_line) {