When I have an instance of Google Chrome active/running on my MacBook Pro (O/S Mountain Lion),
it seems to take about a minute, from the time I close my laptop to the time that it actually goes to sleep (indicator slowly blinks in a waxing/waning manner).
I did a 'pmset -g log' to find out what was going on and found this:
0/2/13 10:14:08 AM EDT Sleep Clamshell Sleep Sleep: Using BATT (Charge:99%) 17 secs
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
Next, I did a second test where I exited 'Google Chrome' using Command-Q and then tried the sleep test again. This time, it took well under 10 seconds for it to go to sleep.
By the way, my pmset -g settings are:
Active Profiles:
Battery Power -1*
AC Power -1
Currently in use:
halfdim 1
sms 1
hibernatefile /var/vm/sleepimage
Hibernate Free Ratio 5
disksleep 10
sleep 0
hibernatemode 0
ttyskeepawake 1
displaysleep 2
acwake 0
lidwake 1
it seems to take about a minute, from the time I close my laptop to the time that it actually goes to sleep (indicator slowly blinks in a waxing/waning manner).
I did a 'pmset -g log' to find out what was going on and found this:
0/2/13 10:14:08 AM EDT Sleep Clamshell Sleep Sleep: Using BATT (Charge:99%) 17 secs
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
10/2/13 10:14:08 AM EDT Timedout Kernel: Response from Google Chrome He timed out 30000 ms
Next, I did a second test where I exited 'Google Chrome' using Command-Q and then tried the sleep test again. This time, it took well under 10 seconds for it to go to sleep.
By the way, my pmset -g settings are:
Active Profiles:
Battery Power -1*
AC Power -1
Currently in use:
halfdim 1
sms 1
hibernatefile /var/vm/sleepimage
Hibernate Free Ratio 5
disksleep 10
sleep 0
hibernatemode 0
ttyskeepawake 1
displaysleep 2
acwake 0
lidwake 1