Mac: Do not ask to handle power events in processes with no PowerManager.

Mac: Do not ask to handle power events in processes with no PowerManager.

Otherwise Chrome causes a 30-second delay trying to put a Mac to sleep.

Only the main browser process, and nacl processes, create a
PowerMonitorDeviceSource. However, renderers and other processes still
call the static function PowerMonitorDeviceSource::AllocateSystemIOPorts.
This results in the process asking to receive power change
notifications, but not hooking up a function to acknowledge them. This
results in 30-second timeouts while trying to sleep a Mac.

This change removes plugin, renderer, utility and worker processes from
the list of process types that register to receive power change events
from OS X.

BUG=132336
TEST=Put a Mac to sleep with Chrome running. After waking, run `pmset -g
log` from Terminal. There should be no new entries for Chrome under
applicationresponse.timedout [10.6] or on a `Timedout` line [10.8]

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=227148

[tapted, 2013-10-04 07:31:47]

Hi Adam, Brandon - please take a look. But feel free to take the bug off me and
roll a better fix. This isn't really my area, but I've verified this works for
me locally.

This may have come about in http://crrev.com/215381

more details at http://crbug.com/132336#c60

(Also note I might be asleep by the time you get this to review (GMT+10)

[agl, 2013-10-04 14:39:34]

LGTM for OWNERS iff bajones is happy with it.

[bajones, 2013-10-04 21:05:06]

On 2013/10/04 14:39:34, agl wrote:
> LGTM for OWNERS iff bajones is happy with it.

LGTM, thanks for addressing this.

[commit-bot: I haz the power, 2013-10-04 22:21:08]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/tapted@chromium.org/25954005/1

[commit-bot: I haz the power, 2013-10-05 00:19:49]

Change committed as 227148