Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Why is Chrome Forcing my MBP to use Discrete Graphics?!
- Thread starter AdDaMan
- Start date
- Sort by reaction score
The chrome helper used to come on for flash video and animations, now it turns on to help with animations for Chrome in general. (Hence, it's a chrome helper app.) Use power switching if it's a problem, just keep in mind that if you switch between discrete and integrated while Chrome is running flash will get goofed up.
I have the same problem too! before I upgraded to ML, last time I checked chrome doesn't use discrete graphics. but after I upgraded to ML, chrome only uses discrete graphics. it's really annoying cause it's eating my battery life twice as fast.:/
There is another issue.
When I have 26" monitor plugged on Thunderbolt it forces Discreet ATI 6770 and if i choose integrated my second monitor goes off and doesnt show anything.
Anyone found way aroud that. I'd love to have it running on integrated as much as possible.
When I have 26" monitor plugged on Thunderbolt it forces Discreet ATI 6770 and if i choose integrated my second monitor goes off and doesnt show anything.
Anyone found way aroud that. I'd love to have it running on integrated as much as possible.
Most browsers these days are implementing hardware acceleration, and due to OS X's way of determining whether the discrete graphics should be used or not, it will switch over.
Unless Apple create some way for developers to specify that the discrete graphics card is not required when making specific API calls that normally trigger the switch, it's going to happen more frequently, especially as apps are updated to support retina displays. (apps will benefit from graphics acceleration much more at higher resolutions)
Unless Apple create some way for developers to specify that the discrete graphics card is not required when making specific API calls that normally trigger the switch, it's going to happen more frequently, especially as apps are updated to support retina displays. (apps will benefit from graphics acceleration much more at higher resolutions)
Hey guys,
i think i found an solution.
goto about:flags and look for GPU-Compositing in all pages and deactivate it.
i think i found an solution.
goto about:flags and look for GPU-Compositing in all pages and deactivate it.
It's not a google problem. OS X itself is enabling the GPU when certain libraries in OS X are called.
Yes, you can probably stop chrome enabling it by turning off chrome features, but that is side-stepping the real problem.
The GPU auto switching in the MBPs is mildly retarded.
IMHO - on battery, the discrete GPU should be turned off 100% of the time. You get horrible battery life with it enabled - and anything that requires it to run well will kill your battery in under an hour anyway.
The MBAs and other macs get by without a discrete gpu for most of the tasks i use my machine for on battery. There should at least be a tickbox in the power settings for "force integrated graphics on battery" or similar.
(yes i know about gfxcardstatus. doesn't mean apple shouldn't fix it themselves)
Chrom is still forcing me into using the discrete graphics on my Early 2013 rMBP. Has this been fixed and somehow I don't have the fix or is this still happening for others?