diff options
author | cjhopman@chromium.org <cjhopman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-11-15 20:26:43 +0000 |
---|---|---|
committer | cjhopman@chromium.org <cjhopman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-11-15 20:26:43 +0000 |
commit | df630986834eb937ea75be5a62b9b9eee6c8ca32 (patch) | |
tree | 3b7617b2820a4ee8bc4d46ad32ab84198c9cfdc4 /base/location.cc | |
parent | 896443ab2572df762937af04661eec3305c83434 (diff) | |
download | chromium_src-df630986834eb937ea75be5a62b9b9eee6c8ca32.zip chromium_src-df630986834eb937ea75be5a62b9b9eee6c8ca32.tar.gz chromium_src-df630986834eb937ea75be5a62b9b9eee6c8ca32.tar.bz2 |
Ensure that the foreground tab's process has high priority
To reclaim memory, Android will kill renderer processes before killing
the browser process (See
http://developer.android.com/guide/components/processes-and-threads.html).
That is, the browser process is a foreground process while the renderer
processes are service processes. A foreground process can bind to a
service process so that that process has the same priority as the
foreground process (in terms of what should be killed).
BUG=159980
Review URL: https://chromiumcodereview.appspot.com/11361252
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168007 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/location.cc')
0 files changed, 0 insertions, 0 deletions