Mac freezes solid when waking up from sleep

Question

Level 1

0 points

Mac freezes solid when waking up from sleep

My new MacBook Pro (bought in January 2015) often freezes completely after waking up from sleep (i.e., once I re-open the computer lid, after more than minutes of inactivity). When that happens, the laptop remains completely unresponsive. Only possibility is powering the machine off by keeping pressing the power button for a few seconds, and reboot.

Here below a piece of the logs, where I believe the error may reside, as various of these instructions often appear just before freezing.

Help would be deeply appreciated.

###################################################################

23/02/15 22:59:16,213 ntpd[146]: wake time set -0.323301 s

23/02/15 22:59:16,214 discoveryd[48]: Basic Sockets,Warn UDS FD=59 ERROR: Send failed errno=32

23/02/15 22:59:16,230 com.apple.xpc.launchd[1]: (com.apple.ReportCrash.Root[641]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash.DirectoryService

23/02/15 22:59:17,051 discoveryd[48]: AwdlD2d AwdlD2dStartAdvertisingPair: 'XXXXXX' Advertising service started

23/02/15 22:59:17,052 discoveryd[48]: AwdlD2d AwdlD2dStartAdvertisingPair: 'dcaadaefff9525c800000000000008efip6arpa' Advertising service started

23/02/15 22:59:17,000 kernel[0]: Google Chrome He (map: 0xffffff802938a000) triggered DYLD shared region unnest for map: 0xffffff802938a000, region 0x7fff87a00000->0x7fff87c00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

23/02/15 22:59:18,000 kernel[0]: AppleCamIn::handleWakeEvent_gated

23/02/15 22:59:19,000 kernel[0]: AppleCamIn::handleWakeEvent_gated

23/02/15 22:59:21,863 Google Chrome Helper[640]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server

23/02/15 22:59:22,000 kernel[0]: Google Chrome He (map: 0xffffff80283d03c0) triggered DYLD shared region unnest for map: 0xffffff80283d03c0, region 0x7fff87a00000->0x7fff87c00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

23/02/15 23:00:54,000 kernel[0]: kauth external resolver timed out (1 timeout(s) of 60 seconds).

23/02/15 23:01:19,892 pkd[219]: FCIsAppAllowedToLaunchExt [343] -- *** _FCMIGAppCanLaunch timed out. Returning false.

23/02/15 23:01:20,038 login[469]: DEAD_PROCESS: 469 ttys000

23/02/15 23:03:19,322 BezelServices 250.13[64]: __BezelUI_ShowImageMeter_block_invoke failed to contact BezelUIServer due to error 0x10000004: (ipc/send) timed out

23/02/15 23:03:58,000 bootlog[0]: BOOT_TIME 1424729038 0

MacBook Pro with Retina display, OS X Yosemite (10.10.2), 15", 2.8GHz, 16GB RAM

Posted on Feb 23, 2015 3:21 PM

Reply

Answer 1

Linc Davis

Level 10

209,739 points

Feb 23, 2015 5:51 PM in response to maxipi

Quit Chrome and see whether there's an improvement.

Reply

Answer 2

maxipi Author

Level 1

0 points

Feb 24, 2015 11:49 AM in response to maxipi

Thanks for the quick answer.

I quit Chrome, started Safari, and the computer crashed again.

I am attaching below the complete log inbetween the two crashes (sorry if it's so long, but evidently last time I have too drastic in cutting)

At the bottom, I guess just before it crashed, one may see the lines I was discussing above.

Can you see where the problem lies?

####################################################################

24/02/15 09:34:46,000 bootlog[0]: BOOT_TIME 1424766886 0