Find a Question:
Google promises to tackle age-old battery guzzling bug in Chrome on
Google has spent years to a bug in its Chrome browser are that the battery life of laptops on Windows significantly reduces, but the group promises to tackle the problem. Now The problem lies in customizing the system clock tick rate.
The problem was already in 2012 raised and the frequency of the system clock. By default in Windows tickrate to 15,625 milliseconds, while the processor is awakened 64 times per second, so it is ready for arithmetic. Programs can increase the tickrate. “Some applications adapt him to 1ms, so the battery time on a mobile system or may decrease by 25 percent. Such a dramatic decrease in battery time is not desirable”, warns Microsoft.
Adapting to 1ms is exactly what Chrome does and at first it seemed that the browser did this at sites with Adobe Flash content only, but users complained that Chrome is the interval in many other cases, reduced to a thousand times per second. The bug has to do with the program visible ClockRes . The problem is that the browser directly set this value when opening and no longer adjusts. Other browsers also fit the tickrate to 1ms to browse in some activities, but for example, Internet Explorer and Firefox returns the system clock tick rate back to 15.625 milliseconds when the activity ends or the user closes the tab.
Chrome users have to close the entire browser, found a Forbes journalist who cranked the problem after years. The renewed attention has been given Priority 1 bug in the Chromium development and across PCWorld tells Google to tackle the problem. Incidentally repaired the Chrome developers a similar defect already in 2008.Viewing:-150
Answer this Question
You must be Logged In to post an Answer.
Not a member yet? Sign Up Now »
Star Points Scale
Earn points for Asking and Answering Questions!