The Final Cut Pro X CRASH Thread

My advice to everyone! (or those that need it!!) and to further my post:

In addition to what I'd previously posted I would advise anyone to think very carefully before installing loads of apps onto a FCPX machine or any Final Cut system for that matter.

Over the many, many years of using both Mac & PC systems in the professional world, computers STILL can NOT 'Happily' have any old thing installed on them. Im sure FCPX is the primary reason for a lot of users whom have bought expensive Apple machines (I for one). So my strong advice is to do what I've always done.. that is Install the minimum number of applications possible alongside your primary apps (FCPX in this case). For example, I found iShowUHD (a great screen capture program!) had made my previous installation of FCP7 stutter on playback. It took me some time until i realized iShowUHD was leaving the odd piece of code running when I looked into the system resources! Memory was being used etc.. A cacellation of the bacground task solved the problem. These kinds of problems are very difficult to spot and can cause any number of problems. This is also the case with many other apps on both platforms.

Apple apps are a safe bet on an Apple Machine with Final Cut! If you are installing 3rd party stuff particularly from not so well known vendors; Games or Compression apps that bugger with codecs and/or leave utilities running in the background etc.. then expect problems. Computers are NOT perfect! You gotta' treat the installation of the Final Cut (ALL Versions) with care even if it does seem a little annoying! Think about what you are installing and install to a CLEAN FRESHLY OS X installed HDD.

This is how I believe Ive kept my installations of primary apps (like FCPX) 'stable'.. or at least stable enough for me to work productively!

I hope this works for some people ;-) Happy Editing!

Just ordered AVID after weeks of trying to create a workflow with FCX... My clients made it clear they will not set through another session with FCX... I did hangin for a few weeks. Now I will stop buying apple products until the bugs are worked out... Very sad to move on but I must support my family and apple let me and about 40 of my editor friends, down, big time!

Something is wrong at apple... They don't care anymore...

I understand what you are saying, but I can't agree, just because I have never been particularly careful about not mixing it up on a mac - in fact, I tend to go crazy - throwing all MS-like caution to the wind! For example, for FCPX & Lion, I created our studio's new FCPX/Lion image by starting with a fresh install of SL (10.6.7 or 8?), then FCPX, then FCS3 (following a few precautions there), then all the 3rd party apps: Adobe CS Master, ProTools, Office, iWork, Plugs, bla bla bla - loading it up with everything we could possibly need. Then just recently, I added Lion to the mix and spent a little time updating. Next I tested the crap outta the image and find just about everything to be peachy keen, even on older iron.

So I think what I love the most about macs, is the (or perhaps, my) ability to be lucy goosy without really bad things happening. Contrasted to my days with PCs, where I was regimented and tight, and bad things ALWAYS happened anyway - I have to say I like things better today's way - So go have fun!

Thank you so much man, this is exactly the correct answer for me as well,a bug for sure. Thanks for figuring out the inspector had to be closed! untill this get fixed, this is the best solution. THANK U = )

Regards,

Kevin

You should not be required to have a lean machine in today's world of computing. Yes, a few years ago you had to be careful what others app you installed.

The only thing dragging my mac and grinding it to a halt is fcpx. Atrocious!!!!

In my 12 years of mac ownership and running apple's software, I have never experienced anything like this.

I rarely complain, but really need to vent some frustration here even if apple doesn't visit this forum.

Back-round rendering is absolute rubbish. I would rather wait for rendering to be done and then carry on with my work, rather than struggling though at snail pace and killing my macbook PRO!!! (It doesn't feel very pro right now ).

I really cannot see any bug fixes resolving and making this software useable any time soon.

Rant done.

And another thing.

As an amateur video maker, I still expect my software to work.

I chose final cut because it's what the professionals use/used.

If I find that the pros are slowly walking away, I'll be slowly following behind them.

I'm prepared to pay the right money for the right software.

What upsets me the most is spending many hours with my head stuck in the manuals and having to re-learn software from scratch, as I did when I left Cubase after financial outlay and even more investment of my time.

Mine crashed last night through my editing, i was running optical flow and it died.

i have lost my project. GONE!! 3hrs work of cutting gone!!! however i still have the project in my projects folder. But when it comes to opening FCPX its not there..

how do i get it back

you can see it here? its the f1 montage

Any ideas?

Don´t worry, i lost 50hrs of work... I tried everything, but the projectfile is corupt and i had to start it new.

You can try to fix the corupt project with this software:

http://www.digitalrebellion.com/promaintenance/

FCPX crashes while openig the project, right?

Then you have to move the complete project out of the fcpx projects folder.

hmm doesnt crash while opening the project. It doesnt like it...but doesnt crash.

When opening fcpx back up, the event is there still...but it asks me to create a new project. Ill give that software a go...if not ill start again. Its not like im making a living from it...good practice i guess haha

I had the problem of having FCPX crash when trying to edit titles/generators already in the timeline . I fixed it by going to the Window menu and click Revert to Original Layout. It seems to "take care" of this problem.

Hope some of this may save time. Sorry it's not a solution though.

I have two machines, one Mac Pro running OS 10.6.8, (3Gb RAM) one MacBook Pro running Lion (2Gb RAM).

FCPX installed on both. Never had older versions of FCP before.

Numerous projects either partially or fully completed in iMovie'11. Source material was DV (Canon Mv800).

Project format in each was widescreen 25fps PAL.

Everything runs smoothly in iMovie on both machines.

FCPX crashes every time I try to import any iMovie project or the iMovie events.

Almost always, it is thread 0 that crashes. Here is a typical error log snippet:

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

0 com.apple.Flexo 0x00000001008ef055 DVFormatReaderCreateFromStream + 2757

1 com.apple.Flexo 0x00000001008ebab4 -[FFMovieInstanceFig _openMovie] + 308

2 com.apple.Flexo 0x00000001008eb60a -[FFMovieInstanceFig initWithURL:] + 106

3 com.apple.Fig.provider 0x00000001100a84df 0x11009d000 + 46303

4 com.apple.Flexo 0x0000000100743364 -[FFProvider _sourcesMakeIfNil] + 452

5 com.apple.Flexo 0x0000000100742048 -[FFProvider sourceKeys] + 24

6 com.apple.Flexo 0x00000001007434f5 -[FFProvider firstVideoSource] + 53

7 com.apple.Flexo 0x0000000100743b46 +[FFProvider providerHasValidSourceForURL:] + 182

8 com.apple.Flexo 0x0000000100d63d6b -[FFMediaEventProjectData newAnchoredSequenceFromURL:manageFileType:keywords:validateFiles:] + 811

9 com.apple.Flexo 0x0000000100d650a5 -[FFMediaEventProjectData addClipsFromURLs:manageFileType:processNow:warnClipsAlreadyExist:isImportingFro mImovie:keywordSets:validateFiles:] + 485

10 com.apple.Flexo 0x0000000100bd0f0b -[FFIMovieImporter newAnchoredObjectForEdit:inSequence:] + 1355

11 com.apple.Flexo 0x0000000100bca919 -[FFIMovieImporter proccessEdit:targetSequence:forStart:duration:withPrevTransDuraton:withNextTran sDuraton:error:] + 681

12 com.apple.Flexo 0x0000000100bd1884 -[FFIMovieImporter editSpineItemToSequence:edit:withMovie:editInfo:atTime:withFrameDuration:withPr evTransDuraton:withNextTransDuraton:error:] + 132

13 com.apple.Flexo 0x0000000100bd38b0 -[FFIMovieImporter collectTimingAndEditToSeq:edit:withMovie:editInfo:atTime:withFrameDuration:with PrevEdit:withNextEdit:error:] + 368

14 com.apple.Flexo 0x0000000100bd93fe -[FFIMovieImporter processEditListInEditInfo:toSeq:error:] + 478

15 com.apple.Flexo 0x0000000100bc9fc6 -[FFIMovieImporter importToSeq:displayName:error:] + 102

16 com.apple.Flexo 0x0000000100bd11b1 +[FFIMovieImporter actionImportWithURL:project:event:error:] + 241

17 com.apple.FinalCut 0x0000000100036896 -[PEAppController importiMovieProject:] + 710

18 com.apple.AppKit 0x00007fff80699eda -[NSApplication sendAction:to:from:] + 95

19 com.apple.prokit 0x00000001002f77ed -[NSProApplication sendAction:to:from:] + 100

20 com.apple.Flexo 0x00000001008c6028 -[FFApplication sendAction:to:from:] + 104

21 com.apple.AppKit 0x00007fff806be46a -[NSMenuItem _corePerformAction] + 365

22 com.apple.AppKit 0x00007fff806be1d4 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 121

23 com.apple.AppKit 0x00007fff80943cf4 -[NSMenu _internalPerformActionForItemAtIndex:] + 35

24 com.apple.AppKit 0x00007fff807f59e9 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 136

25 com.apple.AppKit 0x00007fff806a099c NSSLMMenuEventHandler + 321

26 com.apple.HIToolbox 0x00007fff821197f7 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1002

27 com.apple.HIToolbox 0x00007fff82118d46 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 395

28 com.apple.HIToolbox 0x00007fff82136a81 SendEventToEventTarget + 45

29 com.apple.HIToolbox 0x00007fff82165c35 SendHICommandEvent(unsigned int, HICommand const*, unsigned int, unsigned int, unsigned char, void const*, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 387

30 com.apple.HIToolbox 0x00007fff82192a0a SendMenuCommandWithContextAndModifiers + 56

31 com.apple.HIToolbox 0x00007fff821929c2 SendMenuItemSelectedEvent + 101

32 com.apple.HIToolbox 0x00007fff821928d2 FinishMenuSelection(SelectionData*, MenuResult*, MenuResult*) + 150

33 com.apple.HIToolbox 0x00007fff82173c27 MenuSelectCore(MenuData*, Point, double, unsigned int, OpaqueMenuRef**, unsigned short*) + 467

34 com.apple.HIToolbox 0x00007fff8217337c _HandleMenuSelection2 + 453

35 com.apple.AppKit 0x00007fff80571851 _NSHandleCarbonMenuEvent + 236

36 com.apple.AppKit 0x00007fff80545362 _DPSNextEvent + 1908

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

38 com.apple.AppKit 0x00007fff8050a68f -[NSApplication run] + 395

39 com.apple.prokit 0x00000001002fa04b NSProApplicationMain + 267

40 com.apple.FinalCut 0x0000000100002138 start + 52

On restarting FCPX, the event appears, as does the project. However, there are no clips visible. Sometimes, FCPX will crash again if I click on either the event, the project or the timeline. This can be fixed by trashing the FCP projects and Events folders.

I moved the iMovie project and events folders to the MBPro and repeated the process, with the same results.

Other things I have tried:

I built an iMovie project using just a couple of titles and a transition. That imported into FCP OK.

I have imported some footage shot on an iPhone into iMovie & built a simple project. This could then be imported into FCP with no trouble.

I imported original DV footage from the camera directly into FCP and it had no trouble with it. (This is the same footage that in an iMovie project crashes FCP)

I have tried running both systems as lean as possible, with no other background processes or 3rd party apps.

I always run FCP on it's own, no other apps running.

I have turned off background rendering and all the analysis options for importing.

I have deleted the two FCPX plist files, as suggested by an Apple tech.

I think that about covers my experiences with FCPX so far.

Looking for a solution soon to justify the expense. (I am based in Australia - the price of FCP dropped 10% a few days after I bought it. :-( )

HTH

Hi Mac_It

I gueess the problem is in your imported iMovie DV -Files. See here:

https://discussions.apple.com/thread/3135004

I had the same problem (on a 13" MacBook Pro, 4Gb RAM, 2.3GHz i5), and the same solution worked for me. Many thanks for sharing!

One thing that i found causes the export process to fail every time, that was also an issue with FCP is using the wrong KhZ rate 44 instead of 48 000 for any audio content mainly MP3's brought in from a library.

A good reason to import at this as a minimum.

I can vouch that FCPX does seem the most glitchey bit of apple software i have ever used.

Mine has just crashed - during the last few minutes of importing a 90 minute DV tape from a Sony DV player! All seemed to be going fine until almost the end of the tape.

I sent the crash report off to Apple - where can I find it on my computer to post a copy here? I looked in library/logs/CrashReporter - but not sure if that is correct. Anyway, I could not copy the details!