You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

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

Hello,


I just formatted my MacBook Pro and installed a fresh installation of Yosemite. I always have this bug which makes my log file full:


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


I can give you a hint that it's maybe about Software Updater Helper.. but dunno how to solve it.


Thanks,

JF

MacBook Pro (Retina, 13-inch, Early 2013), OS X Yosemite (10.10)

Posted on Oct 29, 2014 10:34 PM

Reply
97 replies

Dec 8, 2014 3:39 AM in response to hsul

As I stated previously, the suhelperd is the software updater helper that checks for updates. if you look into the Console while opening the App Store and clicking on the Update button, you will see thousands of messages of the Bug directly. I would suggest to turn off the automatic update by going to system preferences and then App Store and uncheck "Automatically check for updates" checkbox. This will help diminishing the amount of messages pushed and coming out from this process, but nevertheless might not help in fixing the issue. But give it a try, it reduced mine and try always to keep the App Store application closed and only open once a week in order to check of any updates..

Yesterday when I was working in Safari, suddenly I've got a frozen Macbook and I waited for it 10 seconds after it restarted automatically unfortunately.. I don't know when apple wanna release a new update fixing those issues which become crucial nowadays..

Dec 8, 2014 4:08 AM in response to JF-

I get a lot of the same.

I'm starting to believe that Apple hired the Windows Vista team to make Yosemite, and combined it with their usual arrogance when it comes to fixing customers' problems.


I get most of these messages during boot time; Yosemite is insanely long to boot (2-3 minutes), tons of disk activity, but nothing in the log to show for it.

Dec 8, 2014 4:33 AM in response to ThomasD3

I'm feeling sorry and I regret that I upgraded to Yosemite. I was reading on the following link: http://appleinsider.com/articles/14/12/04/apple-issues-second-os-x-10102-yosemit e-beta-with-wi-fi-fixes and I found out that the upcoming 10.10.2 is only for fixing WiFi issues. Again ?? WiFi issues again ?? What about all other crashes that we are facing .. God bless Mavericks was happy totally and I was happy as well in the design which I'm lacking nowadays .. as the guys designed Yosemite to be cartoon like windows 8..


Time to downgrade to Mavericks which gonna happen tonight and I don't want the new features even 😟 . I want a stable OS X !

Dec 9, 2014 5:43 AM in response to JF-

I have the same issue on a Mid-2011 Mac Mini. Lots of apparent kernel panic related spontaneous reboots, plus my machine gets stuck in a reboot loop that only seems to be solved by booting into safe mode, and then rebooting.


I suspect it's GPU related because the reboots (if the machine does start up) seem to be correlated to changes in resolution.


Kernel messages:

Dec 8 17:18:44 BUG in process suhelperd[179]: over-released legacy external boost assertions (0 total, 0 external, 0 legacy-external)

Dec 8 18:43:20 ** GPU Hardware VM is disabled (multispace: disabled, page table updates with DMA: disabled)

Dec 8 18:43:21 Previous shutdown cause: -128

Dec 8 18:43:26 BUG in process suhelperd[185]: over-released legacy external boost assertions (1 total, 1 external, 0 legacy-external)

Dec 8 18:44:10 BUG in process suhelperd[185]: over-released legacy external boost assertions (0 total, 0 external, 0 legacy-external)

Dec 8 19:03:52 ** GPU Hardware VM is disabled (multispace: disabled, page table updates with DMA: disabled)

Dec 8 19:03:53 Previous shutdown cause: -128

Dec 8 19:03:57 BUG in process suhelperd[172]: over-released legacy external boost assertions (1 total, 1 external, 0 legacy-external)

Dec 8 19:04:51 BUG in process suhelperd[172]: over-released legacy external boost assertions (0 total, 0 external, 0 legacy-external)

Dec 8 20:02:42 ** GPU Hardware VM is disabled (multispace: disabled, page table updates with DMA: disabled)

Dec 8 20:02:42 Previous shutdown cause: -128

Dec 8 20:02:46 BUG in process suhelperd[170]: over-released legacy external boost assertions (1 total, 1 external, 0 legacy-external)

Dec 8 20:03:28 BUG in process suhelperd[170]: over-released legacy external boost assertions (0 total, 0 external, 0 legacy-external)

Dec 9 14:53:21 Previous shutdown cause: -128

Dec 9 14:53:25 BUG in process suhelperd[184]: over-released legacy external boost assertions (1 total, 1 external, 0 legacy-external)

Dec 9 15:19:04 ** GPU Hardware VM is disabled (multispace: disabled, page table updates with DMA: disabled)

Dec 9 15:19:04 Previous shutdown cause: -128

Dec 9 15:19:09 BUG in process suhelperd[182]: over-released legacy external boost assertions (1 total, 1 external, 0 legacy-external)

Dec 9 15:19:38 BUG in process suhelperd[182]: over-released legacy external boost assertions (0 total, 0 external, 0 legacy-external)

I have created Mac Mini, Yosemite reboot loop (** GPU Hardware VM is disabled) for my issue, since it may be more the just the suhelperd problem.

Dec 11, 2014 1:01 AM in response to JF-

I have the same issue, with multiple auto-reboots and the "Bug in process ..." code in console at the time of these reboots. Another thing that may or may not be relevant is that my Finder now asks to allow incoming network connections on start-up. I had been running 10.10.1 for some time before either of these problems emerged.


I am running a Mac Pro 3,1 (early 2008), with OS X 10.10.1, and a retro fitted ATI Radeon HD 5770.

Dec 23, 2014 8:42 AM in response to smartov

Having this same bug and kernel panic shutdowns


I've been noticing it when running iTunes. First was when Match was running, turned that off and it seemed to have solved the issue. Then it began when I tried to update an iPod and noticed that any peripheral(iPhone, iPad, etc) would cause a beach ball of death. My problem seems to be iTunes related though as i don't recall having any issues running safari or other programs as of yet.


This is really starting to drive me bonkers as i'm trying to do a full restore on my iPhone 6 that also started to have issues, yet i can't get past the simple connection process. getting about 10 crashes a day


mid 2010 17" macbook pro

2.53 Intel core i5

Nvidia GeForce GT330m

Dec 23, 2014 1:41 PM in response to Robotitude

Hi,


i've stayed off this discussion for a while, trying to collect more data on what i see when i get a crash (which happens less frequently, but still happens, and always happens in essentially the same way).


some quick observations.


  • all the reports we have are over a variety of machines manufactured at different times and delivered with different OS X versions. i was starting to think that having upgraded from 10.6 to 10.7 to 10.8 to 10.9 to 10.10 had something to do with it, but reports in this group seem to suggest otherwise.
  • i've begun a daily routine of restarting and immediately killing suhelperd from the Activity Monitor. however, the suhelperd messages have already appeared over 100 times during startup before i even log in, so if suhelperd is really the thing that's doing the damage, said damage is already done. (and it could be the case that by killing suhelperd, i've laid the groundwork for a future crash.)
  • although killing suhelperd makes me and some others feel better, i think we've all been talking about a symptom rather than a cause. even after killing suhelperd, the crashes continue and all belong to the WindowServer. when the WS aborts, there can be no choice other than logging everyone out and leaving you at the login screen with a restart of the WS (assuming you get one, which i always do).
  • all crashes recently (post killing of suhelpderd) have happened when opening an app (usually it's Safari, but not always) or perhaps a system window (e.g., a save dialog). all leave a WindowServer crash log, which has almost always the same collection of messages. none of the console sequences includes a suhelperd message (which i've killed, but perhaps an now an unseen contributor for not running), and all include a variety of messages from the WS before it rides off into the Yosemite sunset.


i'm convinced that the WindowServer is the true culprit. i can almost tell now when i do something that involves a complicated visual transition (opening an app, logging in) whether the crash is coming: it's just that slight pause not expected (or in the case of opening Safari, the bouncing in the dock stops, no window appears) and (wait for it) BOOM.


Happy holidays everyone ... let's hope a debugged 10.10.2 is in our future.

J.


iMac mid 2011

OSX 10.10.1

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

Dec 27, 2014 3:19 AM in response to JF-

Hi all,


I've only recently encountered this issue on a MacBookPro8,3, running 10.10.1. I first discovered that the laptop had seemingly failed to go to sleep while I was using it unplugged for a short period (and had plugged it back in to top off the charge). The machine refused to wake from sleep, and I could feel that there was a lot of heat being vented by the (very active) fans.


After a forced power cycle, I had enough stability to notice the console messages, before I got the dreaded beeps of doom (and corresponding flash of the sleep light) and a frozen machine (kernel panic without the grey screen) and a subsequent forced reboot. The laptop had happily powered, passed POST, and was at the desktop (actually having restarted all my apps), so I was fairly sure it wasn't a memory issue, but wasn't about to rule out memory or logic board issues.


I then got stuck in a reboot cycle, where the machine kept rebooting, getting to the desktop, re-establishing connections, and reloading apps, before beeping, freezing, and force-rebooting.


Getting worried that the machine was headed for an early demise, I'd managed to load this discussion thread in Safari prior to one of the intermediate forced shut-downs, and wondered what might have been different to cause the issue.


In my case (may not be the same for everyone), the different thing that had happened to the machine over the last few days was connection to a weak Wi-Fi network (not one I control). Two iPads (different generations) sat next to the laptop showed one bar of strength, at best, or no connection whatsoever, but the laptop kept showing a full-strength connection. Normal internet and other network-related tasks seemed to work fine (most of the time), if slow at times. I had my doubts about the actual reliability of the internet connection, but didn't think it would influence the machine so badly (which had been rock-solid up to that point).


On the next reboot, I turned off the Wi-Fi as soon as I could, and the machine happily continued to start up, and I had every indication that my stability was back. I switched to an alternate internet connection (3G USB dongle) and have had zero issues since.


Of note, I have had the System Update process hung for a number of days (I sleep my system rather than shut it down), including moving the system across multiple Wi-Fi, fixed, and 3G dongle network connections. It has only been on the flaky Wi-Fi network that I had any system stability issues (and resultant crashes).


Where is this story headed?

- Firstly, it seems that there's a potential kernel issue with the networking or Wi-Fi stacks (leaning towards Wi-Fi), particularly with flaky connections (perhaps an issue at one of the lower layer connections) and the software update side of the system.

- While my experience may not be the same as yours, consider removing ALL network connections from your machine next time it forces a reboot, including physical links. Once the system is back up and stable (if possible), reintroduce network connections one at a time until the failures happen again. That will show up the connection that is failing or having the strange issues.

- Sit back and wait for Apple to patch.


Of course, you experiences may vary, but years of operating Apple products have taught me that sometimes there are many different and complex symptoms for the same relatively simple underlying issue.

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

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.