Issue 94141 in chromium: Accelerated GPU causes battery drain
chro...@googlecode.com
Owner: ----
Labels: OS-Mac Area-Undefined Pri-2 Type-Bug
New issue 94141 by philip.p...@gmail.com: Accelerated GPU causes battery
drain
http://code.google.com/p/chromium/issues/detail?id=94141
Google Chrome 14.0.835.109 (Official Build 97804) beta
OS Mac OS
WebKit 535.1 (branches/chromium/835@93569)
JavaScript V8 3.4.14.15
Flash 10.3.183.5
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_1) AppleWebKit/535.1
(KHTML, like Gecko) Chrome/14.0.835.109 Safari/535.1
Command Line /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
-psn_0_442476 --flag-switches-begin --enable-print-preview
--flag-switches-end
Executable Path /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Profile Path /Users/philip/Library/Application Support/Google/Chrome/Default
What steps will reproduce the problem?
1. Fire up the Chrome browser.
What is the expected result?
System continues to use the integrated (low power) graphics.
What happens instead?
System switches to the (high power) discrete graphics card.
Please provide any additional information below. Attach a screenshot if
possible.
To see the problem you really need to install gfxCardStatus which shows
which graphics cardis in use.
Chrome appears to be using accelerated graphics permanently, which forces
OS X to switch to the discrete graphics card. This reduces battery life
considerably.
Safari appears to only use accelerated graphics when required (usually by a
plugin).
Viewing google+ in Safari switches to the discrete card due to the
GoogleTalkPlugin -- would be nice if it didn't.
Best possible solution: only request HW acceleration when really required.
Acceptable solution: restore the flags to allow turning off HW acceleration.
chro...@googlecode.com
Status: Duplicate
Mergedinto: 88788
Comment #2 on issue 94141 by vange...@google.com: Accelerated GPU causes
battery drain
http://code.google.com/p/chromium/issues/detail?id=94141
(No comment was entered for this change.)