The issue seems to be that Google’s web browser, Chrome, doesn’t release system resources when not doing anything. It does this by setting a high “system clock tick rate” of 1 millisecond and the setting keeps this value all the time. Internet Explorer also sets a high clock tick rate when needs to perform heavy tasks, but unlike Chrome, IE returns the default value of 15.625 milliseconds. Now based on Microsoft documentation, having a tick rate of 1 millisecond causes higher power consumption by up to 25% depending on the scenario. The bigger problem is that according to Forbes contributor, Ian Morris, this clear bug in Chrome isn’t recent, as there are bug reports that go back to 2010. Thanks to the newly published report, Google has finally released an official comment saying that the company is working to fix the bug, and because of the attention it is getting, the Chrome team has escalated the priority; as such we could be seeing a fix very soon. Source PCWold All content on this site is provided with no warranties, express or implied. Use any information at your own risk. Always backup of your device and files before making any changes. Privacy policy info.
