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..d33333b3d41060388b2e7575b15ddbde74e4b339 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"
@@ -224,6 +225,11 @@ void ChromeBrowserMainPartsWin::ShowMissingLocaleMessageBox() {
                  MB_OK | MB_ICONERROR | MB_TOPMOST);
 }
 
+void ChromeBrowserMainPartsWin::PostBrowserStart() {
+  ChromeBrowserMainParts::PostBrowserStart();
+  BeginModuleVerification();

[Finnur, 2013/09/20 14:23:14]

So... we decided (when I changed the module enumerator to run always on XP at
startup) to start that on a delay, so as to not let the ModuleEnumerator
affected startup. The delay in that case was supposed to be 45 seconds (see
comment from cpu): https://codereview.chromium.org/15969017/

This will start the module enumeration much sooner, no? My worry is that this
could be right in the middle of the startup whirlwind and adversely affect it.

[erikwright (departed), 2013/09/24 17:33:51]

I added a delay here.

+}
+
 // static
 void ChromeBrowserMainPartsWin::PrepareRestartOnCrashEnviroment(
     const CommandLine& parsed_command_line) {