Crash using expose after 10.12.2

Question

Level 1

11 points

Crash using expose after 10.12.2

Hello,

I just bought the new 15 inch MacBook Pro 2016 2.6GHz Intel Core i7 with Intel HD Graphics 530 1536 MB and 16 GB 2133 MHz LPDDR3 for memory with 1TB for storage.

After updating it to macOS 10.12.2, I have been experiencing crashes when using expose. For expose, the screen will go black in certain parts and nothing is responsive. I am not able to bring any of the open windows out of expose and they remain stuck in place. It only goes away after you restart the computer.

The computer also freezes up sometimes if I open up my download stack. For the downloads folder crash on the dock, the download thumbnails disappear when fanned out on the dock and they remain stuck fanned out. This also only gets fixed temporarily once the computer is restarted.

Is anyone else experiencing these problems?

MacBook Pro, macOS Sierra (10.12.2)

Posted on Dec 16, 2016 5:09 AM

Reply

Answer 1

78asg

Level 1

4 points

Dec 22, 2016 2:39 AM in response to itsperth

I have the same problem with a MBPR 2016 13" i5. The only way to end the 'freeze', is to start Terminal and kill the Dock, using the following command:

killall -KILL Dock

Reply

Answer 2

Dec 28, 2016 1:11 PM in response to itsperth

Same issue here, can't access any apps, including terminal, when stuck in those mode. As you mentioned, seems related to Expose and the Downloads folder in dock (I'm guessing its a bug with Dock, as Expose is controlled by the dock process).

Reply

Answer 3

itsperth Author

Level 1

11 points

Dec 28, 2016 2:00 PM in response to RMartinez93

I ended up doing a clean install of the OS, did a SMC reset, did a NVRAM reset, and took it to the apple store where they performed a clean install of the OS again. The problem still persisted. At the apple store they also checked out all the hardware and it all came back as working. I'm assuming it was a defective product unless the bug is in the OS build itself. I ended up returning the 15" Macbook Pro 2016 for a new one.

I have attached some pictures of the bug here.

Reply

Answer 4

Dec 31, 2016 12:20 PM in response to itsperth

I'm going to hold out for a while, at least until the next update, on the chance it's a software bug. I have found that when I notice things start to get wonky, if I "killall -KILL Dock" in Terminal as suggested above, the issue goes away. It isn't a fix but leads me to believe it's likely a software issue. Hoping it gets addressed...

Reply