Does Google Chrome have a significant impact on MacBook battery life compared to other browsers?

Battery Life is different than Battery Duration. Battery life will be tied to the maintenance and usage you give to a battery. To put it simply, if your battery is designed to be charged 100 times before it dies (cycles), then using the 100 charges in one month will be the same as using them in 1 year. (or almost the same, since there will be a small loss of power when the battery is idle).

What I mean is, the battery life shouldn't be greatly affected by any application's usage pattern. But…

The truth is that battery duration is definitely affected by the power consumption. In other words: the more the power your computer uses, the less the batter will last with charge, before it requires to be recharged.

With that logic in mind, Chrome is a moderately CPU intensive application on its own (a tradeoff that is inherited by its One Process Per Tab design). It taxes your hardware a little bit more when creating new tabs and it uses slightly more RAM in order to keep things smooth. In exchange, you have a very solid -hard to crash- browser that will be able to keep working even if some of its tabs are literally dead.

Despite that, however, Chrome has Flash (as an extension you can disable). It uses the "same" Flash, but bundled internally. If chrome uses some more battery (something that I have yet to see in real life), Flash uses probably all the battery you can throw at it, but not because Flash needs battery, it's because it needs CPU power, a lot, all the time. CPU power needs electricity. Batteries have Electricity. In the absence of a power outlet, guess who's there to provide juicy power to that hungry CPU? Yes, mamma battery.

So Flash will definitely decrease your battery charge duration (and in turn, it will force you to cycle charge your battery more often, therefore decreasing its life), but this will also happen on Safari, Camino, Firefox and possibly other applications or browsers that use Flash.

I'm not familiar with any issues with the MacBook. With a MacBook Pro (15" or 17" mid-2010 model and later), Chrome forces the use of the nVidia graphics card which drains the battery quicker than if it were running off the Intel HD graphics card.

I've been using gfxCardStatus (http://codykrieger.com/gfxCardStatus) to correct the issue. I have it set to force Intel HD Graphics mode when running off the battery.

Sources:

• http://code.google.com/p/chromium/issues/detail?id=43138
• http://code.google.com/p/chromium/issues/detail?id=45457

Same with the MacBook Pro 2011 (I have 15"). Working from Safari yields more battery than with Chrome and this is with Integrated graphics being forced using Cody's program.

The multi process and "more memory up front" design are what add to the drain. Don't get me wrong, it's a great browser but the reason it's great is that it requires slightly more resources up front compared to other browsers.

Apparently, Chrome 16 resolves this issue to some degree. Earlier versions of Chrome always forced the discrete video card to be activated, while Chrome 16 appears to enable discrete graphics when necessary (e.g. playing Flash), but it will leave the integrated graphics system active when higher graphics power is not needed.