JF-
Level 1 (0 points)

Q: 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

Close
JF-

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

  • All replies
  • Helpful answers

first Previous Page 3 of 7 last Next

  • by Govvy,

    Govvy Govvy Dec 4, 2014 4:37 PM in response to Delawaremathguy
    Level 1 (0 points)
    Dec 4, 2014 4:37 PM in response to Delawaremathguy

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

  • by Steve Dutton,

    Steve Dutton Steve Dutton Dec 6, 2014 7:11 AM in response to JF-
    Level 2 (364 points)
    Mac OS X
    Dec 6, 2014 7:11 AM in response to JF-

    This problem just started showing up . . . I had installed Yosemite's first update over a week ago.

  • by JF-,

    JF- JF- Dec 7, 2014 6:30 AM in response to Steve Dutton
    Level 1 (0 points)
    Dec 7, 2014 6:30 AM in response to Steve Dutton

    Seems I will rollback tonight to Mavericks ... and I'm tired waiting for no reply and no feedback from Apple !

     

    Anybody has any idea if any beta version of 10.10.2 is coming out and what will handle as fixes ?

  • by hsul,

    hsul hsul Dec 7, 2014 11:51 PM in response to JF-
    Level 1 (0 points)
    Dec 7, 2014 11:51 PM in response to JF-

    just killed suhelperd in activity monitor.

     

    and. ignore safari for a while (most of the crash happen when i'm using safari).

     

    apple please speed up the update.

     

    i'm having 10+ crash a day.

  • by JF-,

    JF- JF- Dec 8, 2014 3:39 AM in response to hsul
    Level 1 (0 points)
    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..

  • by ThomasD3,

    ThomasD3 ThomasD3 Dec 8, 2014 4:08 AM in response to JF-
    Level 1 (8 points)
    Mac OS X
    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.

  • by JF-,

    JF- JF- Dec 8, 2014 4:33 AM in response to ThomasD3
    Level 1 (0 points)
    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 !

  • by ThomasD3,

    ThomasD3 ThomasD3 Dec 8, 2014 5:30 AM in response to JF-
    Level 1 (8 points)
    Mac OS X
    Dec 8, 2014 5:30 AM in response to JF-

    that's the worst: there is no new feature in Yosemite that I really use or care about!

  • by Thatdamncat,

    Thatdamncat Thatdamncat Dec 9, 2014 5:43 AM in response to JF-
    Level 1 (0 points)
    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.

  • by Govvy,

    Govvy Govvy Dec 9, 2014 1:45 PM in response to JF-
    Level 1 (0 points)
    Dec 9, 2014 1:45 PM in response to JF-

    I have now noticed that running Chrome instead of Safari seems to have addressed the multiple shutdowns per day. Will continue monitoring to see if it recurs but at present it is now looking like a Safari issue, is there a debug method to delve further into Safari issue?

  • by hsul,

    hsul hsul Dec 9, 2014 6:44 PM in response to Govvy
    Level 1 (0 points)
    Dec 9, 2014 6:44 PM in response to Govvy

    +1 to this.

     

    i have running with chrome since the crash, and the crash frequency reduced to minimum.

     

    uncheck "Automatically check for updates" not doing anything for me, so i revert setup back to default.

  • by Matt_Chrome,

    Matt_Chrome Matt_Chrome Dec 11, 2014 1:01 AM in response to JF-
    Level 1 (0 points)
    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.

  • by smartov,

    smartov smartov Dec 11, 2014 8:27 PM in response to JF-
    Level 1 (0 points)
    Dec 11, 2014 8:27 PM in response to JF-

    Having the same problem. Blackout type shutdowns happen in the middle of doing something. Usually I do something CPU and memory intense when it happens.

    MacBook Air (13-inch, Mid 2012)

  • by Robotitude,

    Robotitude Robotitude Dec 23, 2014 8:42 AM in response to smartov
    Level 1 (0 points)
    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

  • by Delawaremathguy,

    Delawaremathguy Delawaremathguy Dec 23, 2014 1:41 PM in response to Robotitude
    Level 1 (0 points)
    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

first Previous Page 3 of 7 last Next