Those drivers most likely want to do things with the GPU they've never done before ; ) The overflow of graphics processing patches from all our favorite companies indicate this was a widespread disruption.
Why this is happening (educated opinion):
Features were pulled and then reintroduced in these betas, effectively creating a 1:6 chance of getting everything right. From Microsoft down to DisplayLink, each new driver patch comes with a High Sierra disclaimer for this reason.
Then came the upgrade nightmares we see now (overflowing console errors from above features since abandoned, etc.). None of which existed on the beta releases and somehow appear on clean installs and upgrades.
What you can do trace the bug:
(Look in your utility folder or CMD+Space to find these two applications)
- Launch Activity Monitor and look to see if kernel_task is eating memory (indicative of runaway/unresponsive process)
- Open Console and navigate to the errors and faults tab
- Monitor the 'all messages' log when you launch an app known to crash to pinpoint what may cause the issue
Other things that may help:
- Delete the cache folders from these applications in all system and user folders; it helped me. The requests were pulling in bad .plist data.
- Reset the PRAM (command+option+p+r)
- Reset the SMC if you connect peripherals or use USB-C power
- Contact Microsoft directly for support (good luck).
- Going outside for a moment and contemplate downgrading to 10.13.4 if you're not actively developing for the new macOS on that machine.
Looking forward to the next release as well as a response from Apple regarding several of these tickets.
