Model: MacBookPro6,2, BootROM 0C, 2 processors, Intel Core i7, 2.66 GHz, 4 GB, SMC 1.58f17 System model name: MacBookPro6,2 (Mac-F22586C8) Kernel Extensions in backtrace (with process name corresponding to current thread: kernel_taskĭarwin Kernel Version 10.8.0: Tue Jun 7 16:33: root:xnu-1504.15.3~1/RELEASE_I386
The report of the problem is listed below. This week the problem appears more and more often (about 5-6 times per day). Since last year it started crashing frequently with a black screen.
#Gfxcardstatus 2.3 pc mac os x#
That has always been the case, and is a lot easier to avoid (most app makers avoid frivolous use of Core Animation).I have a macbook pro Mac Os X 10.6.8 with processor 2,66Ghz Intel Core i7. CA in turn opens an OpenGL context, which 100% always enables the discrete GPU.
So the last *remaining* cause for dGPU is when applications use OpenGL *or* Core Animation. Now that’s no longer the case! WHAT A RELIEF! The issue that Apple has fixed in 10.12.3 was that the mere existence of certain versions of certain frameworks ( without the app even opening any OpenGL contexts) marked the app as “needs dGPU”. The recompiled version linked somewhere in this thread is still recommended, however, because it contains bugfixes not merged into the abandoned official version. Previously, the only way to fix it was to re-compile it with newer frameworks.
GfxCardStatus 2.3 (last official version): When Core Animation was removed from the app (in a private build), the application no longer required the discrete GPU. Uses Core Animation, which is the cause of it. MacOS 10.12.3 contains some fixes to Apple’s frameworks! There’s been a development on that front, so I’m writing to make you all aware. This is regarding the state of previous dual-GPU MacBook Pros again.
0 kommentar(er)
