The Final Cut Pro X CRASH Thread

I am still in the situation that I even can't start Final Cut X Pro. Maybe someone is so kind to give me an advise based on my crash log? Thanks in advance.

+++++++++++++++++++++++++++++

Process: Final Cut Pro [27048]

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 [2437]

Date/Time: 2011-07-08 11:33:20.250 +0200

OS Version: Mac OS X 10.6.8 (10K540)

Report Version: 6

Interval Since Last Report: 160707 sec

Crashes Since Last Report: 2

Per-App Interval Since Last Report: 47 sec

Per-App Crashes Since Last Report: 1

Anonymous UUID: 077C4430-FEEC-4B48-9298-8E857FD0D756

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000040

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

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

0 libSystem.B.dylib 0x00007fff83dba257 pthread_mutex_lock + 31

1 libSystem.B.dylib 0x00007fff83dfb66e readdir_r$INODE64 + 81

2 com.apple.P2Plugin 0x000000012347c9d5 TimecodeAddTimecode + 245

3 com.apple.P2Plugin 0x00000001234761f4 P2AnalyzePulldown + 24580

4 com.apple.proapps.MIO 0x00000001015c8077 -[MIORADPluginManager pathIsValidVolume:] + 167

5 com.apple.proapps.MIO 0x00000001015c47ab -[MIORADManager pathIsValidVolume:] + 27

6 com.apple.Flexo 0x00000001009af51c -[FFStorageManager refreshAvailableVolumes] + 1692

7 com.apple.Flexo 0x00000001009ad898 -[FFStorageManager RADManagerAvailable:] + 24

8 com.apple.Foundation 0x00007fff87142bc5 _nsnote_callback + 167

9 com.apple.CoreFoundation 0x00007fff87d77000 __CFXNotificationPost + 1008

10 com.apple.CoreFoundation 0x00007fff87d63578 _CFXNotificationPostNotification + 200

11 com.apple.Foundation 0x00007fff8715a54f __NSThreadPerformPerform + 219

12 com.apple.CoreFoundation 0x00007fff87d6c401 __CFRunLoopDoSources0 + 1361

13 com.apple.CoreFoundation 0x00007fff87d6a5f9 __CFRunLoopRun + 873

14 com.apple.CoreFoundation 0x00007fff87d69dbf CFRunLoopRunSpecific + 575

15 com.apple.qmaster.SwampCore 0x0000000137b3f4e1 startDaemon + 978

16 com.apple.qmaster.SwampCore 0x0000000137b4075b startQmasterServices + 24

17 com.apple.compressor.StompUI 0x0000000137664b1d startSwampServices + 9

18 com.apple.CompressorKitMAS 0x0000000137102797 -[CKClusterBrowser start] + 28

19 com.apple.FinalCut 0x00000001000355e7 -[PEAppController applicationDidFinishLaunching:] + 1783

20 com.apple.Foundation 0x00007fff87142bc5 _nsnote_callback + 167

21 com.apple.CoreFoundation 0x00007fff87d77000 __CFXNotificationPost + 1008

22 com.apple.CoreFoundation 0x00007fff87d63578 _CFXNotificationPostNotification + 200

23 com.apple.Foundation 0x00007fff87139b26 -[NSNotificationCenter postNotificationName:object:userInfo:] + 101

24 com.apple.AppKit 0x00007fff8010744a -[NSApplication _postDidFinishNotification] + 100

25 com.apple.AppKit 0x00007fff8010737f -[NSApplication _sendFinishLaunchingNotification] + 66

26 com.apple.AppKit 0x00007fff801d235d -[NSApplication(NSAppleEventHandling) _handleAEOpen:] + 219

27 com.apple.AppKit 0x00007fff801d1fd9 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 77

28 com.apple.Foundation 0x00007fff871711c6 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 360

29 com.apple.Foundation 0x00007fff87170ff6 _NSAppleEventManagerGenericHandler + 114

30 com.apple.AE 0x00007fff818ff32b aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 162

31 com.apple.AE 0x00007fff818ff224 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 32

32 com.apple.AE 0x00007fff818ff12b aeProcessAppleEvent + 210

33 com.apple.HIToolbox 0x00007fff84e8d619 AEProcessAppleEvent + 48

34 com.apple.AppKit 0x00007fff800d7095 _DPSNextEvent + 1191

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

36 com.apple.AppKit 0x00007fff8009c68f -[NSApplication run] + 395

37 com.apple.prokit 0x00000001002fa04b NSProApplicationMain + 267

38 com.apple.FinalCut 0x0000000100002138 start + 52

Thread 1: Dispatch queue: com.apple.libdispatch-manager

@strava:

Perhaps you have a corupt file in your final cut events or -project folder.

Move your Projects files e.g. at the desktop and try to start fcpx. If it crashs, make the the same with the files from the event folder. Then try again.

I bought FC pro X. First time I regret to have giving my money to apple. Crash on Crash and often I loose a lot of work. It seem it crashe when I edit text. Each time I use accentuated caracter "^". Mine is in french.

Unless this big problem, the new approach of editing is really wonderful. Hope that program will run in a few month perfectly.

Accent marks on foreign language keyboards seems to be a real problem. It's come up on the forum before.

I just had my first crash after almost three weeks. It happened when I was importing a "bad" clip. It was a clip that I had converted from .mts to AIC a long time ago with one of the demo converters I was trying out at the time. The clip has always been a bit wonky and gave me some trouble in FCE.

You can prevent the potential for a crash just by simply turning off Background Rendering.. this helped on my MAcPro 2006.

i agree ...as ingesting iMovie events seems to search for all available event without further user dialogue, I could

not test the hypothesis if DV files are causing the issue. however, something tells me that this may be the root cause for at least the crashes on may machine. And btw I am importing from an external HD with FW800 ...

I had Final Cut Pro X permanently crashing with DV files. So I called Apple Support and after analysing my logs they suggested to me to do a clean install of MacOS X and Final Cut Pro X on a separate partition.

With the installation on the new partition I was able to cut my DV files without a single crash.

I don't know what caused the crash on my original installation. It was a 5 year old installation with one migration from an core duo based MacBook to a i5 based MacBook Pro.

@ Uli. W.

Have the DV Clips been in PAL? Are you in Germany?

Have you been able to import an existing iMovie Bibliothek with your new partition?

Thanks for Feedback

Yes and yes, the DV clips have been PAL and I'm from Germany.

I haven't used iMovie very often so I only had a few iMovie Projects. On the new partition I could import them without any crash and with a lot less of cpu usage.

Hi, I have a crash problem too. I install the FCPX before lion and was crashing sometimes and now after the upgrade its crashing all the time, if I open a project, try to use text or just play the project. It is really ennoying!

thanks,

Izabella

Yes (DV digitized from S-VHS) ... I am living in Switzerland. ;)

Think I will also go through a clean install as I had several versions of FCE and FCP on it and some hidden files may still be around.

I have started using Final Cut Pro X, after being so very sad and mad with apple for caring little about all of us. FCPX, It worked for about a week and then it stopped exporting... Now it crashes every time I try and add or delete a title on the timeline.

I did just put in Lion and everything went wrong after that... Any Help!

Apple seems to be no help these days with any problem...

Having the exact same thing after upgrading to Lion. Whenever I edit, delete or even touch a title in my timeline, I get the beachball, and then FCPx quits unexpectely.