summaryrefslogtreecommitdiffstats
path: root/third_party
diff options
context:
space:
mode:
authorjeremy@chromium.org <jeremy@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-07-27 13:16:54 +0000
committerjeremy@chromium.org <jeremy@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-07-27 13:16:54 +0000
commit4643342df1a699719c5c900f91d789d2f8105764 (patch)
treed94c26230d70fbaef735b2b83170550f11242600 /third_party
parentebd19b7213b2b1242ef9874013a5e72d4e6530fb (diff)
downloadchromium_src-4643342df1a699719c5c900f91d789d2f8105764.zip
chromium_src-4643342df1a699719c5c900f91d789d2f8105764.tar.gz
chromium_src-4643342df1a699719c5c900f91d789d2f8105764.tar.bz2
[Mac] Make Chrome not delay system sleep
Some processes [e.g. the GPU process] do not set up a SystemMonitor object, since the startup code was changed to always allocate the Power notification IO port [http://codereview.chromium.org/7235023/] these processes were causing a delay in sleep as the power manager was trying to contact the process. This change whitelists the IO port allocation in ChromeMain() to only include process types that allocate a SystemMonitor which fixes the sleep issue. If a process not in the whitelist attempts to use the SystemMonitor it will hit a DCHECK in a debug build and the error will be ignored in release (see SystemMonitor::PlatformInit()). BUG=88867 TEST=When Chrome is running, Macs should sleep immediately. Review URL: http://codereview.chromium.org/7491038 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@94279 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'third_party')
0 files changed, 0 insertions, 0 deletions