It's probably some weird, deeply rooted bug in the hardware acceleration functions that would require to employ specialized tracing and debugging tools that's sending a specific function call into a black hole or causes GPU resources to run out. I'm not a Mac guy, but perhaps playing with your display settings can fix it. Enforcing a lower screen resolution to safe resources might have benefits just as may running the programs in windowed mode or on their own virtual desktops. It may just cost performance. Anyway, nothing is lost by trying.