A long known bug in Google Chrome is finally to be fixed. In the default settings, Windows generates a timer interrupt 64 times per second. These are used to react to certain events such as keystroke inputs or mouse clicks. The value is a compromise: on the one hand, the CPU leaves enough time for the CPU to enter the power saving mode, but on the other hand, it can react quickly enough to normal inputs.
If it is even faster to go, then can be rotated on this screw, which also for example game manufacturers regularly use. Chrome has also set the so-called "system clock tick rate" since version 22 of 2008 to 1,000 interrupts per second. This was a very desirable behavior that benefited the reputation of the Google browser as a particularly fast browser, but also increased the power consumption.
The problem is, however, that the higher interrupt rate in Windows applies system-wide and is not reset. Thus even a user and minimized browser for the whole system allows the increased power consumption. As early as 2008 there was a first error report on this behavior in the Chromium project, which should be corrected in 2010, however. In 2012, however, the message "Google is not battery-friendly on Windows" appears again.
Reading tip: Chrome vs. Firefox Internet Explorer 10
It is now reported that Google wants to make the mistake seriously. A development version with the appropriate patch should already exist. When the correction will find the way to the current distribution is still unknown.
No comments:
Post a Comment