1

Ever since I upgraded from my old MacBook Air 2012 to a brand new MacBook Pro I feel really disappointed with how my computer works.

It used to occasionally freeze, overall work more slowly (!), and the thing that is making me frustrated most of all: Sleep Wake Failure.

I tried to copy the log from console here but the text is too long.

Here is a screen shot of a console. I will try to insert anything that is needed here.

console

  • Are you able to get to an Apple Store and see an Apple Genius? Given the recent age of the computer, they should be able to help. – Graham Miln Aug 2 '15 at 10:23
  • Take a look at New rMBP sleep/wake failure crashes. Sadly it looks like you are not alone. – Graham Miln Aug 2 '15 at 10:27
  • Possible duplicate of apple.stackexchange.com/questions/119423/… – Graham Miln Aug 2 '15 at 10:28
  • Insufficient information to help you. Regardless how long the log is paste it on one of the places like dropbox. Include the log from the Console all messages from the point "wake reason".. Sorry, with the limited information you provided one can not even begin to analyze. – Ruskes Aug 2 '15 at 15:08
  • Start with providing us your system profile using the etresoft.com/etrecheck In most cases it is some 3d party app responsible, since Apple does sufficient testing to have discovered fundamental problem like Sleep/Wake. – Ruskes Aug 2 '15 at 15:12
1

The next time you have an issue, run sysdiagnose by pressing the key chord for it or manually from terminal and then open a support ticket with Apple. Much of the diagnostic information in console.app requires one of two things to be useful:

  • Access to Apple's source code and internal support documents
  • Access to a large volume of logs from dozens (or ideally hundreds or more) of Macs to use a tool like splunk to collect and analyze various logs to identify patterns of error messages to trace back issues like this to root causes.

In the mean time, use old-fashioned pen and paper to make a note of the wall clock time when the Mac is slow and look at Activity Monitor / top and perhaps collect one sysdiagnose each time you notice the Mac being slow. Once you have 10 incidents, you might have enough data to know what processes are making your experience poor and determine if your slowness is related to:

A good place to start on that monitoring is using top or vm_stat to run when before you notice the slowness and then review for data once you notice that the Mac has actually slowed down.

OS X: Memory usage freaking me out

I would also write down what you wanted to do and what other apps were running when you notice slow downs. This will come in handy to identify if you can simply adjust the workload or need to make other changes to achieve better performance.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .