BUG in process suhelperd: over-released legacy external boost assertions (1 total, 1 external, 0 legacy-external)

UPDATE! I performed a clean wipe and fresh install on my hard drive of Yosemite OS X. It DID NOT solve this issue. My computer still restarts and I hit the same 100 "bug in process" in my console. I hope apple fixes this asap.

Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.

Feedback

Or you can use your Apple ID to register with this site and go the Apple BugReporter. Supposedly you will get an answer if you submit feedback.

Feedback via Apple Developer

You are welcome.

I'v been having frequent crashes with both OS X 10.10.0 and 10.10.1 and been finding this "BUG in process suhelperd" message now occurring frequently in the console right about the time that i have a crash.

almost always, it takes only a simple click to open Safari, or a click to start up Mail -- the screen goes into bizarro mode (lots of random rectangular areas with random text and graphics) -- and then i get logged out, as does the other user on the system.

happened three times today.

i've never seen an Apple OS in such a shambles as OS X Yosemite. it's always been rock solid -- until now.

iMac mid 2011

OSX 10.10.1

12G memory, 2.5G Intel Core i5, Radeon 6750M

will absolutely do -- now that i have some sense to look for, especially where my problem almost always on the launch of something (Mail, Safari, Xcode, some others) i'm keeping the console open (regularly clearing so that not too much accumulates) and awaiting the next crash.

regards,

DMG (J.)

Did anybody get a response to this? We just got a new MacBook at work and did a fresh install because it was doing the same thing. Same result though keeps hanging for some reason. I submitted a Radar too

I have the exact same behavior on a 2013 MacBook Air. Since upgrading to Yosemite frequent shutdowns when an app such as Safari is launched. I have the same frequent suhelperd errors in console. I called Apple to try to get some more advanced troubleshooting performed as I have experienced over 20+ shutdowns in a single day and at present my laptop is pretty much unusable so I have reverted to iMac with a prior version of Mac OS X.

The support call got escalated to a 'senior tech' who called me back however they just don't understand how to coherently and methodically troubleshoot this to find the root cause and in the end suggested I install my prior version of Mac OS X. This is very frustrating as on a Windows machine you would have a crash dump which could be analyzed for a very specific cause. Could Apple comment on this and how we get a mature escalation to help you pinpoint a very widespread issue?

hi,

i have sent in feedback to Apple about this problem we're all discussing; and the best i can tell from all the internet searches is that maybe it's related to the 6750M Radeon graphics processor in my machine. apparently, the mid2011 27" iMacs had some sort of recall on their graphics processors (but not the same as my midd2011 iMac 21.5"). the suggestion seems to be that the new OS is pushing a little too hard on the graphics processor -- although i tend not to believe it.

on the other hand, i've had two crashes yesterday and today. both were simply logging in and clicking on Safari after sleep, and both went immediately "BOOM," logging out me and the other user on the machine. the "suhelperd BUG" only appeared in just _one_ of these, so pehaps there's something more here.

today's experience include:

-- user 2's desktop was blank (except for background picture) upon wakeup, despite the fact that it's visually populated with many files and folders. click on the screen and drag, and only then could you see the file or folder you clicked on. i relaunched the Finder. all is now well -- the desktop is repopulated.

-- switch to the login screen, login User #1, click on Safari, and "BOOM." we're both logged out.

i restarted. things have been fine today since then. but after more probing, i noticed these things:

-- Activity Monitor shows that "softwareupdated" is "Not Responding."

-- something i read out there on the internet suggested going to System Preferences --> App Store and unchecking all the boxes. curious: every time i either check or uncheck the box "Automatically check for updates" in the Preferences pane, i immediately see a message in the Console window that says

12/4/14 5:46:43.000 PM kernel[0]: BUG in process suhelperd[206]: over-released legacy external boost assertions (1 total, 1 external, 0 legacy-external)

so is this the direction we all should go? can others confirm this behavior, that a simple click of a box in a Preferences Pane is generating Console messages? if we turn off the preference "Automatically check for updates," will it help?

let's all keep looking.

DMG (J.)

21.5" iMac mid 2011

OSX 10.10.1

12G memory, 2.5G Intel Core i5, Radeon 6750M

I also turned off automatic check for updates and handoff but the shutdowns continue