Posting in the "Best Web-Browser for Mac" inspired me into making this thread.
I guess I'm not the only one whom have noticed one rather irritating things about Google Chrome for Mac OS X. When you do something that makes Google Chrome trigger your MacBook Pro's dedicated graphics card it won't go back to using the integrated one until you completely kill your Google Chrome session entirely.
This might be a non-issue for many of you, but for some of us it's a real pain in the ass really. I for one have a MacBook Pro 17" 2011 model featuring Radeon HD6750M as dedicated graphics card and the Intel HD Graphics 3000 as integrated solution.
In my case I can't think of ANY scenario where the integrated solution wouldn't be sufficient? So why would I want the dedicated card to kick in, making the battery drain ten times worse?
The major problem isn't the fact that the dedicated card kicks in while watching streams, playing flash and things like that, it's the fact that it won't go back to using the integrated card before you kill your Chrome session entirely. If things worked like with Safari whereas the dedicated card only kicks in "when needed" like when watching a YouTube video and then go back to using the integrated one when I finished watching things would be okay I guess. But the problem (Google claims) is that Apple don't provide the necessary tools and API for Google to really optimise how the dynamic graphic switching works with Chrome and that's why we are stuck with a solution like we've got today. There are several reports of this issues, and Google employes themselves have answered a few of them and told there is nothing they can really do about it without Apple allowing them.
This brings me to this thread, and I simply want to force Google Chrome to NEVER EVER activate the dedicated graphics card in the first place. In my situation with a integrated Intel HD Graphics 3000 card there is no reason why I couldn't just stick with the integrated card upon web-browsing 24/7. For other people whom got older MacBook Pro's and poorer integrated solutions there might be situations where a solution like this would not be ideal but in most cases web-browsing will work flawlessly with about any integrated graphics solution on any Mac hardware out there offering dynamic graphics switching in the first place. For other systems this issue will not occur anyway.
To put things in perspective, if I unplug my MacBook Pro 17" 2011 model and use it for web-browsing only with Google Chrome and one of the first things I do is watching a YouTube video my battery will run out almost as fast as if I was constantly watching a 720P video in VLC. It's not only the battery being the problem, you also get a much warmer machine.
Which bring me back to the purpose of this thread, is there anyway I can force Google Chrome to not active the dedicated graphics card at all?
I guess I'm not the only one whom have noticed one rather irritating things about Google Chrome for Mac OS X. When you do something that makes Google Chrome trigger your MacBook Pro's dedicated graphics card it won't go back to using the integrated one until you completely kill your Google Chrome session entirely.
This might be a non-issue for many of you, but for some of us it's a real pain in the ass really. I for one have a MacBook Pro 17" 2011 model featuring Radeon HD6750M as dedicated graphics card and the Intel HD Graphics 3000 as integrated solution.
In my case I can't think of ANY scenario where the integrated solution wouldn't be sufficient? So why would I want the dedicated card to kick in, making the battery drain ten times worse?
The major problem isn't the fact that the dedicated card kicks in while watching streams, playing flash and things like that, it's the fact that it won't go back to using the integrated card before you kill your Chrome session entirely. If things worked like with Safari whereas the dedicated card only kicks in "when needed" like when watching a YouTube video and then go back to using the integrated one when I finished watching things would be okay I guess. But the problem (Google claims) is that Apple don't provide the necessary tools and API for Google to really optimise how the dynamic graphic switching works with Chrome and that's why we are stuck with a solution like we've got today. There are several reports of this issues, and Google employes themselves have answered a few of them and told there is nothing they can really do about it without Apple allowing them.
This brings me to this thread, and I simply want to force Google Chrome to NEVER EVER activate the dedicated graphics card in the first place. In my situation with a integrated Intel HD Graphics 3000 card there is no reason why I couldn't just stick with the integrated card upon web-browsing 24/7. For other people whom got older MacBook Pro's and poorer integrated solutions there might be situations where a solution like this would not be ideal but in most cases web-browsing will work flawlessly with about any integrated graphics solution on any Mac hardware out there offering dynamic graphics switching in the first place. For other systems this issue will not occur anyway.
To put things in perspective, if I unplug my MacBook Pro 17" 2011 model and use it for web-browsing only with Google Chrome and one of the first things I do is watching a YouTube video my battery will run out almost as fast as if I was constantly watching a 720P video in VLC. It's not only the battery being the problem, you also get a much warmer machine.
Which bring me back to the purpose of this thread, is there anyway I can force Google Chrome to not active the dedicated graphics card at all?
