Chrome browse bug poses power problem for portables

Wondering why you are not getting the same battery life [anywhere] near the expected life that is advertised for your laptop?

If you use Google’s Chrome web browser, that could be a reason.

A documented bug in the source code for the Chromium open source project – that has been around for close to two years – seems to account for some of the power drain that has hit users of Chrome browser have been experiencing.

The bug was first included for Chrome version 22, yet Chrome’s developers have so far ignored it.

The bug has to do with how Chrome forces Windows machines to manage processor idle time. When a laptop isn’t doing much, it sends its processor(s) to sleep to save power, waking up every once in a while if there are any events that need handling. For Windows, these wake-ups normally happen every 15.625ms, but that interval can be adjusted. Instead of waking up the processor every 15.625ms, Chrome tells Windows to have it wake up every 1ms. So while your laptop normally wakes up the processor 64 times per second when it’s idle, when you have Chrome running, the processor wakes up 1,000 times per second.

This wouldn’t affect a desktop [except a bit of power consumption] unless you are experience a power failure in the room but have a UPS. In which case, don’t use Chrome during a power failure.

I am wondering sometimes if Google does this on purpose. After all, it is on the competitor’s operating system.


About ebraiter
computer guy

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: