Hacker News Reader

Comment by _xnmw | Hacker News Reader

Seriously regretting the upgrade. Am I the only one having random graphics issues, such as rendering bugs, latency, and freezing, on a multi-monitor setup on a Late 2013 MBP? Lesson learned: always wait a few months after a major version bump.

View on HN

I generally wait until version n + 1 is at least in beta before installing version n. There is rarely a sufficiently compelling new feature to persuade me to risk the stability of my system sooner than that.

(Still pining for Snow Leopard :-)

Initially I was regretting upgrading as well. Crazy high CPU as a 'kernel_task' which in turn made my machine unusable. It would completely lock up.

I ran 'kexstat' via the terminal to check out what kernel extensions I had that might be causing the issues. The only third party extensions I had were VirtualBox and Avira. Uninstalled Avira and now things are buttery smooth.

The window manager now runs on Metal 2, which should give a nice jump in responsiveness, but it is likely responsible for the graphics glitches people have been reporting, especially with older machines.

As a counter-anecdote, I have a rMBP 2012, and I haven't encountered any major bugs (no kernel panics, hangs, lag), though I have seen a few minor glitches (Safari tab bar didn't draw properly, only saw this once). On balance I'm happy with the upgrade however, my system feels more stable and faster as a whole, fixed a few issues from Sierra.

You’re not the only one I’ve heard of, but I haven’t worked a pattern yet. I’d agree with your conclusion though, unless you have two machines wait until the .2 release.

Of course make sure you report the issues to Apple.

MacBook Pro (2014) with two external 4K screens here: Got glitches (some areas of the screen sometimes look like rendered memory corruption).

When I scale the external monitors’ resolution from 1920x1080 Retina to 2560x1440 Retina per monitor, macOS lags heavily and freezes. Sometimes, after a few minutes, it recovers and seems responsive. Then I drag a window and it becomes unresponsive again to the point where it won’t recover and only a hard reboot helps.

Upside: With Metal 2 the fan stays quieter. I can use two 4K screens and won’t get deaf from a jet turbine on my desk. Before High Sierra I connected at most one 4K screen and occasionally disconnected it because the built-in dedicated graphics card got really hot and caused the fan to run at high speeds.

Lots of people are having problems. Check out the replies here:

https://twitter.com/stroughtonsmith/status/91239022851777331...

Always wait a few months. I go out of my way to download the recent OS to my apple app store account in case I need to re-install, and always maintain a carbon copy cloner backup.

Edit: SuperDuper is also a fair alternative to CCC, don't work for either, I forgot bombich owns CCC.

> Am I the only one having random graphics issues

Something was changed in the rendering and CALayer is often nil during viewDidLoad. I assume it will break lots of apps that render custom UI elements.

Having precisely the same problem on precisely the same hardware.

Those issues have been fine with me, and my Late 2013 MBP.

VMWare Fusion + Bootcamp, however...

Same series of machine here. It restarted itself at 8am this morning when the lid was closed and it was on the side. That’s the only problem I’ve seen.

For Fusion and Bootcamp, especially if you converted to APFS, you'll need VMware Fusion 10. Then on top of that you'll have to remove the VM that points to the bootcamp partition and recreate that bootcamp VM.

Some have reported success when using that scenario. Unfortunately not everybody has been that lucky, so far it is unclear why.

I haven't converted my disk yet, but that's good to know.

One more recommendation is to use the "try before you buy" option [0]. You have 30 days to test.

If it works out for you then buy and assign the license to the install and the time limit will be removed (so no need to reinstall)

[0] http://www.vmware.com/products/fusion/fusion-evaluation

Keep an eye on this thread [0] at the VMware Fusion forum.

Seems that it depends on if you installed Windows 10 by BIOS or EFI. For BIOS installed configurations you would have to disable SIP in order to use the bootcamp partition as a VM.

Hopefully VMware finds a better solution.

[0] https://communities.vmware.com/thread/572924

If these are bad enough, they are sometimes fixed by a fresh install (which has the effect of reseting settings to High Sierra defaults).

I restarted into MacOS for the first time since March, updated to High Sierra...wiggled around a little bit still feeling this operating system is pretty much abandonware at this point.

Restarted back into bootcamp Windows 10 minutes later.

I'll be back next March to poke around some more.

I can't see MacOS existing in 1-2 years in its current form. Apple will unify everything and move to ARM.

I almost see this as a fact at this point.

Reply on news.ycombinator.com