Yositimy

Q: Anyone seeing crashes after 10.11.6 update

The 10.11.6 update seems to have caused a return of stabilization effect crashing issue in our recently built 8 core dual D700 32GB RAM MacPro. I have had FCPX crashes during stabilization of all 4 projects run since the update. Seems to crash toward the end of the last clip in the project. Two seem to be a dispatchqueue thread, one seemed to be a dominantmotiontrackerworker thread, and the other seems to be a GPU reset by the kernel. Anyone seeing similar crashes?  These are simple 20 to 60 minute long projects with 6-10 clips. Nothing fancy.

Posted on Aug 8, 2016 8:31 PM

Close

Q: Anyone seeing crashes after 10.11.6 update

  • All replies
  • Helpful answers

  • by BenB,

    BenB BenB Aug 9, 2016 4:21 AM in response to Yositimy
    Level 6 (9,816 points)
    Video
    Aug 9, 2016 4:21 AM in response to Yositimy

    Same system, latest version of FCPX, not seeing any issues.  An hour long Project with only 6-10 clips?  That's not simple, that's TONS of stabilization analysis data to be built.  What is the duration for each clip?  What percentage of free space is on each of your drives?  I assume you're not running off the system drive, but a secondary drive, which is recommended, especially for hour long programs.

  • by Yositimy,

    Yositimy Yositimy Aug 9, 2016 6:29 AM in response to BenB
    Level 2 (243 points)
    Desktops
    Aug 9, 2016 6:29 AM in response to BenB

    Simple in that only stabilization and fast forward effects are used. The one hour long project actually crashed after all the work was done and FCPX was sitting idle. The other projects range between 5 and 15 minutes, which is still a lot of processing. Individual clips are generally ~2-3 minutes. During the same period I also have done dozens of one hour projects without issue. These only have cuts, blurs, and some transcode. I can run handbrake for hours at full speed (~1500% CPU indicated by activity monitor) without issue, also compressor. Its just FCPX that seems to crash. FCPX may be the only one that uses the GPU as a helper.

     

    The source video is imported to a library on a 1TB thunderbolt SSD (samsung pro), the only thing on that drive, maybe 70% free.  The internal 1TB storage is also about 70% free.

     

    I was thinking perhaps a hardware or GPU failure as was discussed on the MacRumors forum, but the GPU is not reseting in all cases. Before I go off and run the diagnostics test, or reload the OS, I wanted to check if others are seeing the same thing.  FCPX seemed to work fine under 10.11.5, rarely an issue.  Perhaps I'll try putting the library on another drive....  or just live with it.

  • by Yositimy,

    Yositimy Yositimy Aug 15, 2016 11:18 AM in response to Yositimy
    Level 2 (243 points)
    Desktops
    Aug 15, 2016 11:18 AM in response to Yositimy

    Just an update.  I moved the library to another drive, same drive model (Samsung 850 pro), same enclosure. I've run 5 projects without issue. 

  • by Yositimy,

    Yositimy Yositimy Aug 22, 2016 3:20 PM in response to Yositimy
    Level 2 (243 points)
    Desktops
    Aug 22, 2016 3:20 PM in response to Yositimy

    Well I may have spoke too soon, the first 6 projects ran fine, but I've had three failures on a row since.  Not a confidence booster.  

  • by Alchroma,

    Alchroma Alchroma Aug 22, 2016 11:42 PM in response to Yositimy
    Level 6 (18,906 points)
    Video
    Aug 22, 2016 11:42 PM in response to Yositimy

    Mine has been fine so far.

     

    Al