Google didn't take action until Ian Morris' story gained traction

It seems as though Google issues a new public release of its Chrome browser every few weeks. While we’ve seen plenty of feature creep and performance improvements over the years, one Chrome for Windows bug has gone unpatched for four years.
The battery draining bug was first discovered by Chrome for Windows users way back in 2010 and is related to the “system clock tick rate” according to Ian Morris, a contribute to Forbes. Since the system clock tick rate in Windows can control how often a processor sleeps, it can have a noticeable impact on battery life.
Chrome for Windows sets the system clock tick rate to 1.000ms -- as long as it is open, no matter what the browser is doing -- instead of the customary 15.625ms. Microsoft says that setting the tick rate to 1.000ms can result in up to a 25 percent increase in power consumption, which explains the battery draining issues that Windows notebook users are experiencing when running Chrome.

Morris gives this real world example:
Well, when you open the most recent version of Internet Explorer, the rate stays at 15.625ms until the browser needs to do something where the rate must increase. If you go to YouTube, say, and play a video IE will increase the rate to 1.00ms. When you shut that tab, and carry on with normal browsing, it will return to 15.625ms. In Chrome though, it is increasing the rate as soon as the browser is opened, and it keeps it high until you shut the browser completely.
Following Morris’ article on the subject, Google has finally acknowledged the issue and is working internally to found a solution.

Sources: Forbes via, PC World

"What would I do? I'd shut it down and give the money back to the shareholders." -- Michael Dell, after being asked what to do with Apple Computer in 1997

Most Popular Articles

Copyright 2018 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki