Perhaps if enough people do this, Google will actually take note and look into fixing the problem. This adds a vote for the issue to be looked at, and will also send you updates about the bug, including if it actually gets fixed. The best possible option for Chrome users now is to "star" the issue on the bug tracker. Both IE and Firefox only do so when content like video demands it. I've tested both of these myself, using a tiny utility called Clockres, and I can confirm Chrome is the only one that increases the rate on startup. If Google doesn't take the problem seriously, then the bug will remain, and Windows laptops running Chrome will drain the battery faster than the same machine running Internet Explorer or Firefox. The first report was in 2010, but the last confirmed bug addition was made yesterday. I found out about this bug a long time ago, and it's been raised with Google via its Chromium bug tracker for a long time. Microsoft might address this problem in the future, but it's unlikely to be in a rush when other developers seem able to work around the problem. Pointing that out doesn't solve the problem for Windows users though, and the fact remains that IE and Firefox don't exhibit this issue at all, instead they up the refresh when needed - to play media, say. It's worth pointing out that Macs and Linux machines don't have this problem, because they use something called "tickless timers". A small utility allows you to see the system clock resolution
0 kommentar(er)
