This issue has been recorded as being a Windows issue but I have been seeing this on Mac as well. Will have to check on it and see how to test this on my machine.
There is a serious bug in Chrome that causes the browser to wake up the CPU as many as 1,000 times per second even when idle, thanks to the system clock tick rate being set to 1.00ms by Chrome. This is many times more than the 64 times per second usually observed with the Windows default clock tick rate of 15.625ms. Believe it or not, this bug has been known to Google for many years now and they have just recently decided to deal with it.
As noted on code.google.com:
What steps will reproduce the problem?
1. Just open Google Chrome and navigate to a website with any flash content.
2. System clock tick rate is increased to 1ms
3. Close the website or navigate to page without flash content
4. 1ms tick rate is left forever (until browser is closed)
Seems that Goole Chrome has no system clock tick interval management. Just increases it and keeps forever. Keeping tick rate at 1ms is not recommended. See document:
“If the system timer interval is decreased to less than the default, including when an application calls timeBeginPeriod with a resolution of 1 ms, the low-power idle states are ineffective at reducing system power consumption and system battery life suffers. System battery life can be reduced as much as 25 percent, depending on the hardware platform. This is because transitions to and from low-power states incur an energy cost. Therefore, entering and exiting low-power states without spending a minimum amount of time in the low-power states can be more costly than if the system simply remained in the high-power state.”