Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

Chrome on Mac sucks (electrons), says Google, so we'll fix it

Battery gluttony targeted for code-fixes to keep you feeding data to Google for longer

Mac users will soon be able to run Chrome without watching their battery status fall by the minute, with Google tweaking the code to cut down unnecessary system wake-ups.

The Chocolate Factory's main aim is to stop Chrome being a “battery hog”, according to Peter Kasting.

Kasting, a senior software engineer in the Chrome UI team, writes that Safari “seems to do better” on Macs.

The revisions to the Chrome code-base cover four long-standing complaints about rendering and unnecessary wake-ups.

Rendering priority has been rejigged so that background tabs have a lower priority than foreground tabs. Kasting writes that this can cut the number of idle wake-ups by as much as 50 per cent.

In the second fix, the devs want to remove unnecessary wake-ups for very simple pages. As the original bug report says, merely to open a Google search page Chrome used three times the CPU that Safari needed, because where Safari had nine “timer fires” in 30 seconds, Chrome had 393.

The third and forth fixes address similar issues but on different sites – Capitalone.com and Amazon.

Again, the fixes aim to reduce the number of unnecessary wake-ups when idle, to cut down on CPU usage.

The patches haven't hit the code-base yet but Kasting remarks that “improvements generally move to beta in at most six weeks, then to stable in another six weeks”.

Earlier this month, Google reworked how Chrome handles Flash, again to improve battery life. ®

 

Similar topics

TIP US OFF

Send us news


Other stories you might like