The Final Cut Pro X CRASH Thread

Perfect! Thanks for the advice.

Simon

And yet another update.

Looks like the project I spent a day on is corrupt. I installed FCPX on another computer and it crashes everytime it tries to read that project. Same behavior as this computer.

So, do I start over or do I go back to an older final cut? I lost 1.5 days of work here.

-scott

I followed your advice but it does not help me. Final Cut Pro X crashes everytime I try to start it. This is really disappointing. I am on a Mac Pro 3,1 (2008). I think I followed every advice on this topic but no improvement.

I don't know if you've already done this, but ... I've just got back from the Apple Store, where we discovered a lot of old, leftover components from an old FCP Express install that I had on my laptop. The offending items were ...

AppleInteremediateCodec.component

DdsktopVideoOut.component

FCP Uncompressed 422.component

LiveType.component

It also turned out that I had "Better Battery Life" selected in the Energy Saving control panel instead of "Better Performance". We corrected those 2 issues, and so far FCPX is working with media on my extnal drive without crashing.

Thank you for the suggestions. I cleaned it up and some more components from FCE which still were there but again it crashes during start. If things will not improve I will do a clean install of the OS but only when the lion is released.

Rock solid here on iMac 8,1 and MacbookPro 3,1 (both unsupported). I am using 10.6.8 and would love to test on a Lion beta. I'm thinking things may get scary there, but for now, knock on aluminum, all is well but for a few bugs in both Motion and FCPX - and the crazy new magnetic timeline that I could have lived without. Cheers!

coocoo

Ps. I did a clean install of the OS on a drive, installed FCPX + Motion + Compressor, then added back FCS3. In my mind, this was the way to go (the 4th option left out of the apple KB).

Message was edited by: coocooforcocoapuffs

I am so mad.. i hope apple are working around the clock to bring out some bug fixes because i'm starting to feel like a guinea pig who paid 300 dollars for my trouble.. i've just lost 5 days work... i imported some new audio clips, then it crashed and started crashing on start-up. so i deleted the problem file and i can get it to run, everything accept my main project, and, way to go apple, no earlier saves to try to open and just a corrupt project.. this reminds me of early Premier. Greattt! i feel like a sucker, this app just isn't ready for release and everyone is loosing money and time because apple have been so inconsiderate and arrogant to their loyal public....

Oliver

Does the App crash or does the complete MBP crash?

I had troubles with MPB crash that turned out to be hardware that the distributed diagnostic didn't find.

Give it a try.

Hey bholtzkener,

Just the App and just on the one project, all my other projects run fine.....

Glad your experience has been mostly positive. Right now, in my situation, I cannot rely on MOSTLY. I need an NLE I can completely TRUST. And so far FCPX is NOT that program.

Sure, I can continue to use my old FCP for awhile....even though I've FINALLY got all the long awaited equipment to move forward (with the exception of editing!)

FCPX is unstable. Unreliable. And as such, unusable.

WHY should I continue to bloody myself night after night with lost projects....forgotten autosaves and the mystery of the magnetic storyline and other quirky "improvements"? The next morning is always the same. I open the software and wonder - what was your name again?

A few days ago, I rationalized that APPLE would make this better. Sooner or later.

BUT...

There's only been SILENCE. Why not address this debacle head-on - with information...and honesty....and with a semblance of reassurance that the problems...and concerns are being dealt with. The silence only reinforces the rumors that APPLE has changed. Yeah so...it was always an expensive choice. But it was innovative. Reliable. The choice of artistic pros.

If the company is going to abandon the users carried this platform forward and paid more money for more performance...don't string us along. Have the decency to come out and say we are not a part of the corporation's future.

It's the silence that scares me the most. It has frightened me enough to ditch more than a decade's worth of workflow to seek another NLE.

"Insanity: doing the same thing over and over again and expecting different results."

I give up. I'm moving on. CS5 is ordered.

And, as I sit here and wonder what's really so **** good about this very expensive laptop I just bought...

I'm starting to see a little light through the WINDOWS.

Final Cut Pro X crashes always when importing the iMovie events. In iMovie the events and the clips are working as expected.

@Oliver 10.0

I have the same Problem - corrupted project and no solution: https://discussions.apple.com/thread/3155100

Is this true for all imported iMovie events?

Many, many crashes -- OS version 10.6.8

this last one--I was zooming in to a timeline-- movie is 264, old B&W footage-- about 2 minutes long, so I don't think there is a memory issue. had turned off my airport and closed every other program. Had just rebooted. Perhaps the one thing you can see is, I am nothing if not presistant. I want this program to work! Come on LION!

Crash report begins with ( I have no idea what is useful here--sorry, but didn't want to clog up the page with all the rest of the info)

Process: Final Cut Pro [256]

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

Identifier: com.apple.FinalCut

Version: 10.0 (179114)

Build Info: ProEditor-179110400~1

App Item ID: 424389933

App External ID: 3491984

Code Type: X86-64 (Native)

Parent Process: launchd [107]

Date/Time: 2011-07-07 14:53:26.157 -0500

OS Version: Mac OS X 10.6.8 (10K540)

Report Version: 6

Interval Since Last Report: 360557 sec

Crashes Since Last Report: 24

Per-App Interval Since Last Report: 137807 sec

Per-App Crashes Since Last Report: 13

Anonymous UUID: FF6C6D0D-E320-4B30-9E99-AC583197F9C4

Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x000000014dc1a000

Crashed Thread: 82 com.apple.flexo.worker-thread

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

0 libSystem.B.dylib 0x00007fff88d30a6a __semwait_signal + 10

1 libSystem.B.dylib 0x00007fff88d34881 _pthread_cond_wait + 1286

2 com.apple.QuartzCore 0x00007fff85148271 CAViewEndDraw + 129

3 com.apple.AppKit 0x00007fff830fe71f -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 3516

4 com.apple.AppKit 0x00007fff83077c0e -[NSView displayIfNeeded] + 969

5 com.apple.AppKit 0x00007fff83072aba _handleWindowNeedsDisplay + 678

6 com.apple.CoreFoundation 0x00007fff87001b37 __CFRunLoopDoObservers + 519

7 com.apple.CoreFoundation 0x00007fff86fdd464 __CFRunLoopRun + 468

8 com.apple.CoreFoundation 0x00007fff86fdcdbf CFRunLoopRunSpecific + 575

9 com.apple.HIToolbox 0x00007fff82ac67ee RunCurrentEventLoopInMode + 333

10 com.apple.HIToolbox 0x00007fff82ac6551 ReceiveNextEventCommon + 148

11 com.apple.HIToolbox 0x00007fff82ac64ac BlockUntilNextEventMatchingListInMode + 59

12 com.apple.AppKit 0x00007fff83047eb2 _DPSNextEvent + 708

13 com.apple.AppKit 0x00007fff83047801 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155

14 com.apple.AppKit 0x00007fff8300d68f -[NSApplication run] + 395

15 com.apple.prokit 0x00000001002fa04b NSProApplicationMain + 267

16 com.apple.FinalCut 0x0000000100002138 start + 52

Crashed Thread: 82 com.apple.flexo.worker-thread

You need to post thread 82, not thread 0.