gfxCardStatus
gfxCardStatus copied to clipboard
gfxCardStatus reports the wrong state for which GPU is active
I have a MacBook Pro (15-inch, 2018) with the Radeon 560X. When I connect my external monitors, the dedicated graphics kick on as expected and gfxCardStatus reports this correctly. However when I disconnect my monitors, it still says dedicated when it is actually using the integrated graphics. As you can see below:

I've confirmed that it is indeed the integrated graphics being used by looking at the displays tab in About My Mac
, which is how Apple suggests checking which GPU is active: https://support.apple.com/en-us/HT202053

If I exit and re-open gfxCardStatus the state is correct and it will say integrated again:

Thanks for the report. Similar to #298 in some respects, in that this is either a race condition between the time we get the “display reconfiguration” callback and when the GPU actually switches, or we're just not getting that callback at all for some reason.

I have the same issue. eg, when I change to 'integrated only', it displays as 'discrete only' :P even though, in the screenshot, you can see that it is in fact using the integrated intel gpu.
Cool application by the way :)
@hughperkins Hi, I have the same identical issue. Did you find the cause?
I am seeing this issue as well.
I'm having an issue where gfxCardStatus is reporting integrated graphics is being used when I've confirmed my system is using discreet graphics.
The image below shows the "i" icon while the Activity Monitor reports consistent usage from both graphics cards (bottom is the dedicated graphics card). The "i" icon remained through the entirety of when this graph was recording.

@UIDCLR When your system is in that state, can you capture the output of system_profiler SPDisplaysDataType
and paste it here?
I'm also often experiencing an "i" in the menu bar when in fact the discrete GPU is being used, and vice versa. It doesn't seem to be predictable though, sometimes I disconnect an external monitor from the laptop, the GPU switches to i but the app remains at d, yet sometimes it updates properly.
In those cases when it doesn't update properly, the menu bar icon and "GPU: …" line flatly contradict the dependencies shown:

The output of system_profiler SPDisplaysDataType
in this state is always the same:
Graphics/Displays:
Intel HD Graphics 630:
Chipset Model: Intel HD Graphics 630
Type: GPU
Bus: Built-In
VRAM (Dynamic, Max): 1536 MB
Vendor: Intel
Device ID: 0x591b
Revision ID: 0x0004
Automatic Graphics Switching: Supported
gMux Version: 4.0.29 [3.2.8]
Metal: Supported, feature set macOS GPUFamily2 v1
Radeon Pro 560:
Chipset Model: Radeon Pro 560
Type: GPU
Bus: PCIe
PCIe Lane Width: x8
VRAM (Total): 4 GB
Vendor: AMD (0x1002)
Device ID: 0x67ef
Revision ID: 0x00c0
ROM Revision: 113-C980AJ-927
VBIOS Version: 113-C9801AU-A02
EFI Driver Version: 01.A0.927
Automatic Graphics Switching: Supported
gMux Version: 4.0.29 [3.2.8]
Metal: Supported, feature set macOS GPUFamily2 v1
Displays:
Color LCD:
Display Type: Built-In Retina LCD
Resolution: 2880 x 1800 Retina
Framebuffer Depth: 24-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Automatically Adjust Brightness: No
Relaunching the app then always produces correct results.
If the root cause of this issue can't be tackled, maybe a workaround might be to re-check the active GPU when the dependencies list has been updated? I'm not sure, but that seems to be correct at least most (or even all?) of the time.
(macOS 10.14.6, 2017 MBP, gfxCardStatus v2.5)