MacOS – IOAccelSurface2 error floods console macOS 10.12 Sierra

consolemacmacos

I have a MB Pro that is locking up afer about 30 minutes.
When I open console I find this message but cant figure out what is causing the problem.

fault 12:14:37.463057 -0700 kernel IOReturn
IOAccelSurface2::surface_unlock_options(enum eLockType, uint32_t):
surface is not locked.

Best Answer

We had a user at our company that was having some performance issues on their Mac. So I connected remotely via Timbuktu and took a look at their console. I noticed a constant flood of similar errors:

fault 11:48:36.982151 -0500 kernel IOReturn IOAccelSurface2::surface_unlock_options(enum eLockType, uint32_t): surface is not locked.

So I removed TeamViewer but the errors persisted. After spending about an hour trying to resolve the problem I discovered that the console flood was a "red herring". The flood was being triggered by Timbuktu and my remote connection to the computer. As soon as I disconnected the user told me that the console flood stopped.

Related Solutions

MacOS – When online the webpage becomes unresponsive on the macbook-pro osx

Which browser are you using?

I was experiencing the same issue on Chrome, all I did was

Go into Chrome - Preferences
Go to advanced settings
Un-tick the box "Predict network actions to improve page load performance"
Restarted Chrome

Then it worked fine

Causing an error with getpwuid in Console, and how can I fix it

This question from superuser sounds just like the one that your asking.

https://superuser.com/questions/194094/how-do-i-get-rid-of-com-apple-launchd-peruser-errors-in-my-log

The error that the person gets in that question is just about the same as the one as you are asking except that his UID is 501 where yours is 32752.

The answer i believe that might solve your problem is provided by the user JasKerr:

I can answer your last question, but it will take more work to solve the problem.

The peruser indicates a launchd daemon started by a userland process. The numeric suffix is the UID. In this case, an application attempted load a launchd job as user 501. That failed, since there appears to be no user 501 on your system.

Have you installed software recently? User management utilities changed in Leopard, so an installer intended for an older version (Tiger?) may not work properly in 10.5.6.

Start by taking a look at ~/Library/LaunchAgents, /Library/LauchAgents, and /Library/LaunchDaemons. There may be a job that's UID 501.

If not, you could do a (brute-force) search for an application/file owned by 501:
    sudo find /Applications -user 501 | less
If anything turns up, that will point to the culprit.

Best Answer

Related Solutions

MacOS – When online the webpage becomes unresponsive on the macbook-pro osx

Causing an error with getpwuid in Console, and how can I fix it

Related Question