diff options
| author | grt@chromium.org <grt@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-04 16:50:19 +0000 |
|---|---|---|
| committer | grt@chromium.org <grt@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-04 16:50:19 +0000 |
| commit | c2e19612483e6a11bb67c81b4924168de4bd0908 (patch) | |
| tree | 80959c0632318ecac422f40a008284f66e6567cb /chrome/chrome_installer.gypi | |
| parent | 4dfec746697b565f8b2f5331817896833c149725 (diff) | |
| download | chromium_src-c2e19612483e6a11bb67c81b4924168de4bd0908.zip chromium_src-c2e19612483e6a11bb67c81b4924168de4bd0908.tar.gz chromium_src-c2e19612483e6a11bb67c81b4924168de4bd0908.tar.bz2 | |
Lower the I/O priority of the installer when resonable.
On operating systems that support it (Vista+), begin background
processing mode before doing major disk I/O in the installer if it was
launched below the normal process priority class. One hopes that this
avoids making users' machines unresponsive while an update is being
applied in the background.
BUG=167622
TEST=mostly covered by "setup_unittests.exe
--gtest_filter=SetupUtilTest.Adjust*", but it will also be interesting
to look at verbose installer log files for an install and for a Google
Update-driven update. Only the latter should contain "Entered background
processing mode."
Review URL: https://chromiumcodereview.appspot.com/16023027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@203982 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/chrome_installer.gypi')
| -rw-r--r-- | chrome/chrome_installer.gypi | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/chrome/chrome_installer.gypi b/chrome/chrome_installer.gypi index 16c4d4b..e85d7fc 100644 --- a/chrome/chrome_installer.gypi +++ b/chrome/chrome_installer.gypi @@ -433,6 +433,7 @@ 'installer/setup/setup_unittests_resource.h', 'installer/setup/setup_util.cc', 'installer/setup/setup_util_unittest.cc', + 'installer/setup/setup_util_unittest.h', ], 'rules': [ { |