Use valid /prefetch arguments for process launches on Windows. - do not submit

chrome/installer/util/auto_launch_util.cc

Index: chrome/installer/util/auto_launch_util.cc
diff --git a/chrome/installer/util/auto_launch_util.cc b/chrome/installer/util/auto_launch_util.cc
index e61cf7677d09db1742737d8a22503438c6734145..078c476bfb18108dbca2db338f703530f48ed8f6 100644
--- a/chrome/installer/util/auto_launch_util.cc
+++ b/chrome/installer/util/auto_launch_util.cc
@@ -20,6 +20,7 @@
 #include "chrome/common/chrome_constants.h"
 #include "chrome/common/chrome_paths.h"
 #include "chrome/common/chrome_switches.h"
+#include "chrome/common/prefetch_argument_win.h"
 #include "chrome/installer/util/util_constants.h"
 #include "crypto/sha2.h"
 
@@ -58,6 +59,7 @@ void EnableBackgroundStartAtLogin() {
 
   base::CommandLine cmd_line(application_dir.Append(installer::kChromeExe));
   cmd_line.AppendSwitch(switches::kNoStartupWindow);
+  chrome::AddWindowsPrefetchArgument(&cmd_line);

[gab, 2016/01/18 19:10:52]

Most prefetch IDs will be flexible across versions but this one isn't as it's a
command-line written in the registry. We should note that in the comments where
id 1 is being assigned in AddWindowsPrefetchArgument().

Also, would be nice to retroactively fix already registered command-line
(otherwise this change will initially be a no-op and will very slowly propagate
over-time as people somehow switch out&in of background mode -- or
re-install..).

 
   base::win::AddCommandToAutoRun(HKEY_CURRENT_USER, GetAutoLaunchKeyName(),
                                  cmd_line.GetCommandLineString());