Non NVidia graphics card issues with Adobe and Mountain Lion

Question

It took me a while to figure it out, but now I am certain. If using a Mac with a non nvidia graphics card there will be issues in Mountain Lion while using Adobe products. I tested this with Illustrator CS6 for over a year on 5 different Mac computers.
Here is what happens
As soon as I open Illustrator on a Mac without a NVidia graphics card and I attend to apply an shadow effect, Illustrator crashes. If I do this procedure on a Mac with a NVidia inside, all works well.
I tested this on the following Macs
MacBook Pro (Early 2009) with NVidia 9600M GT - it works
MacBook Pro (Early 2011) with Radeon 6750M - doesn't work
Mac Pro (Early 2009) with Radeo HD 5770 - doesn't work
The same Mac Pro (Early 2009) with NVidia GT120 - it works
MacBook Air (Mid 2012) with Intel HD 4000 - doesn't work
iMac (Late 2012) with NVidia 680MX - it works
Since I owned all these Macs, I could test it several times with different kind of software updates. 10.8, 10.8.1, 10.8.2 and 10.8.3 did deliver the same result. Everytime the same result.
Already got in touch with Adobe
With Illustrator CS5 it worked like a charme, so I assumed it could be an Adobe issue. But Adobe support told me, it's Apple's fault since 10.8 uses different processes for the graphics performance.
What can be done, to resolve this issue? I cannot buy only Macs with NVidia inside, since the small portable front of Macs is only coming with Intel graphics cards. And is there anybody out there, having this issue? I cannot be the only one, using shadows in Illustrator.

Answer 1

With Illustrator CS5 it worked like a charme, so I assumed it could be an Adobe issue. But Adobe support told me, it's Apple's fault since 10.8 uses different processes for the graphics performance.
A typical response.  IMO it's most likely a combination of Adobe's reluctance to fix the issue combined with Apple's desire for advancement and change.  I've personally experienced several things that've become broken owing to Apple changing fundamental aspects of the OS, and the developers of the third-party software in question have either never fixed their software, or are taking their sweet time.  WireTap Studio and Snapz Pro from Ambrosia are a case in point, though they eventually fixed Snapz Pro.  Eventually…
Frankly, good luck getting either side to do anything about this.  Your best bet is probably getting in touch with AppleCare and seeing if you can get this escalated to Engineering, but I wouldn't hold your breath for a fix from either party.  Or perhaps one of the Apple mailing lists will prove useful.