Google To Fix A 4 Year Old Chrome Bug

By | July 18, 2014

Google To Fix A 4 Year Old Chrome BugTalk about priorities.

A battery draining bug that was first reported back in 2010 is now being investigated by Google, according to the reports.

The issue stems from a poorly set system clock tick rate (1.000ms) while Microsoft themselves recommend developers to use (15.625ms). So what does that mean? It means that the processor is being woken up far more frequently that it should be, affecting battery usage by as much as 25%.

The good news? An engineer has already been assigned to investigate the issue and hopefully, fix the 4 year old bug.

[Via: Forbes]

About (Author Profile)

Vygantas is a former web designer whose projects are used by companies such as AMD, NVIDIA and departed Westood Studios. Being passionate about software, Vygantas began his journalism career back in 2007 when he founded Having said that, he is also an adrenaline junkie who enjoys good books, fitness activities and Forex trading.

Comments (2)

Trackback URL | Comments RSS Feed

  1. Tiago Sá says:

    You can say goodbye to Chrome’s responsiveness if they “fix” this “bug”. When Firefox “fixed” it (cause it also had it), I noticed.

    • kież says:

      It’s a matter of at least *restoring* the original/recommended value when Chrome exits. Because right now it DOESN’T