alexrest

Q: Final Cut Pro X crashes when analyzing for dominant motion

MacBook (12-inch, Early 2016) 1.3 GHz Intel Core m7, Intel HD Graphics 515 1536 MB, OS X 10.11.6, Final Cut Pro X version 10.2.3 (276640).

 

I've added 2 or 3 clips to a new project. I turned on the Stabilization effect for each clip and slowed down the clips to 50% speed. After a period of inactivity, FCP performs the background task of analyzing the clips for dominant motion. The progress bar reaches 1% then Final Cut crashes. It's very repeatable; it happens every time. Maybe 1 out of every 5 times it crashes the Mac will also sign out of the user account completely. Here are the problem details:

 

Process:               Final Cut Pro [1659]

Path:                  /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro

Identifier:            com.apple.FinalCut

Version:               10.2.3 (276640)

Build Info:            ProEditor-27664000056000000~1

App Item ID:           424389933

App External ID:       815823966

Code Type:             X86-64 (Native)

Parent Process:        ??? [1]

Responsible:           Final Cut Pro [1659]

User ID:               501

 

Date/Time:             2016-07-25 20:50:47.501 -0400

Report Version:        12

Anonymous UUID:        ABED6519-7A0B-861C-7DA6-831EC40A90C2

 

 

Time Awake Since Boot: 1100 seconds

 

System Integrity Protection: enabled

 

Crashed Thread:        38  com.apple.dominantMotionTrackerWorker  Dispatch queue: opencl_runtime

 

Exception Type:        EXC_CRASH (SIGABRT)

Exception Codes:       0x0000000000000000, 0x0000000000000000

Exception Note:        EXC_CORPSE_NOTIFY

 

Application Specific Information:

abort() called

 

Application Specific Signatures:

Graphics hardware encountered an error and was reset: 0x00000813

 

 

Thread 0:: Dispatch queue: com.apple.main-thread

0   libsystem_kernel.dylib        0x000000011175f43a mach_msg_trap + 10

1   libsystem_kernel.dylib        0x000000011175e887 mach_msg + 55

2   com.apple.CoreFoundation      0x000000010d7e3a54 __CFRunLoopServiceMachPort + 212

3   com.apple.CoreFoundation      0x000000010d7e2ee1 __CFRunLoopRun + 1361

4   com.apple.CoreFoundation      0x000000010d7e2734 CFRunLoopRunSpecific + 420

5   com.apple.HIToolbox           0x000000010fd20a3c RunCurrentEventLoopInMode + 240

6   com.apple.HIToolbox           0x000000010fd20871 ReceiveNextEventCommon + 432

7   com.apple.HIToolbox           0x000000010fd206a6 _BlockUntilNextEventMatchingListInModeWithFilter + 71

8   com.apple.AppKit              0x000000010c16edcd _DPSNextEvent + 1093

9   com.apple.AppKit              0x000000010c87bbbc -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1658

10  com.apple.AppKit              0x000000010c16373c -[NSApplication run] + 926

11  com.apple.prokit              0x000000010852842f NSProApplicationMain + 329

12  com.apple.FinalCut            0x00000001080d2bf0 main + 1344

13  libdyld.dylib                 0x00000001115bf255 start + 1

MacBook, OS X El Capitan (10.11.6)

Posted on Jul 26, 2016 3:34 AM

Close

Q: Final Cut Pro X crashes when analyzing for dominant motion

  • All replies
  • Helpful answers

  • by Tom Wolsky,

    Tom Wolsky Tom Wolsky Jul 26, 2016 5:05 AM in response to alexrest
    Level 10 (118,096 points)
    Apple TV
    Jul 26, 2016 5:05 AM in response to alexrest

    HHow much RAM? What's the media?

     

    first try trashing preferences after every crash. Create a new admin test user and try it there.

  • by David Bogie Chq-1,

    David Bogie Chq-1 David Bogie Chq-1 Jul 26, 2016 7:32 AM in response to alexrest
    Level 7 (25,772 points)
    Video
    Jul 26, 2016 7:32 AM in response to alexrest

    > Exception Note:        EXC_CORPSE_NOTIFY<

     

    Gotta love the coder who slipped that in!

     

    If this corpse crashing continues after you execute Tom's advice, try this:

    1. Create a new project, call it Stabilization.

    2. Place your clips into this new project but trim them to only the parts you will actually need to use (FCP evaluates the entire clip for analysis and that's probably where the problem is).

    3. Share this project to the original format.

    4. Import the shared Stabilization movie.

    5. Apply stabilization to the imported movie.

     

    If FCPX still crashes, you probably have other issues that may not be directly related to the motion analysis.

  • by alexrest,

    alexrest alexrest Jul 26, 2016 9:25 AM in response to Tom Wolsky
    Level 1 (4 points)
    Video
    Jul 26, 2016 9:25 AM in response to Tom Wolsky

    Hi Tom, thanks for your reply.

     

    8 GB of RAM. The video is 1080p 60fps from a GoPro. When the media was imported, I selected the "Create proxy media" checkbox under Transcoding.

     

    Trashing the preferences didn't help. Creating a new admin test user also did not help.

  • by Tom Wolsky,

    Tom Wolsky Tom Wolsky Jul 26, 2016 9:34 AM in response to alexrest
    Level 10 (118,096 points)
    Apple TV
    Jul 26, 2016 9:34 AM in response to alexrest

    WWhat are the exact specs of the media? Did you switch to proxy playback after you created the proxy files? So you're crashing while using proxy media?

  • by alexrest,

    alexrest alexrest Jul 26, 2016 9:38 AM in response to David Bogie Chq-1
    Level 1 (4 points)
    Video
    Jul 26, 2016 9:38 AM in response to David Bogie Chq-1

    Thanks for the reply, David.

     

    I tried what you said (essentially flattening the clips into a movie and then stabilizing in a different project) but FCPX still crashes. Based on the crash details, I'm suspecting it's an issue with the graphics card, right?

     

    Have any other 12" MacBook users reported a similar problem?

  • by alexrest,

    alexrest alexrest Jul 26, 2016 10:19 AM in response to Tom Wolsky
    Level 1 (4 points)
    Video
    Jul 26, 2016 10:19 AM in response to Tom Wolsky

    Media is 1920x1080 59.94p. Not sure what other specs you need. Please let me know.

     

    Yes, I switched to proxy playback after I created the proxy files, but I don't think proxy media has anything to do with it. I tried starting from scratch and importing the clips without proxy media, but that still crashed when motion analysis begins. I've even tried other clips to make sure I'm not working with corrupted media, but FCPX still crashes.

  • by David Bogie Chq-1,

    David Bogie Chq-1 David Bogie Chq-1 Jul 26, 2016 10:36 AM in response to alexrest
    Level 7 (25,772 points)
    Video
    Jul 26, 2016 10:36 AM in response to alexrest

    GoPro, you say?

    Assuming you have a backup of the library, open a fresh new library and import your GP clips but do it only one at a time. Try to stabilize, one clip at a time, and then bring in the next one. I'm betting one of them is a bad transfer from the GP. We get a bad video file from our P2 cards about once in every five or six hundred clips. It's annoying and difficult to track down the culprit file.

     

    You could just reimport your footage from the GoPro assuming you haven't reformatted the card.

  • by Tom Wolsky,

    Tom Wolsky Tom Wolsky Jul 26, 2016 10:39 AM in response to alexrest
    Level 10 (118,096 points)
    Apple TV
    Jul 26, 2016 10:39 AM in response to alexrest

    CCodec and format. The fije extension. The problem seems to be in processing the original media. If there's nothing unusual about the media I would suggest taking it to an Apple Store.