Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Upgraded to FCP 10.2, but cannot update library (crashes)

Yesterday I upgraded to Final Cut Pro X 10.2 (Also upgraded Mac OS to 10.10.3).


Today for the first time, I tried to run FCP and when I did, it asked to update my libraries. But when I said OK, it ran through some process, and CRASHED.


I have read things about restoring fonts (didn't work), removing Plug-ins (not sure how since I cannot launch the FCP app)... then I called Apple and after sitting on hold for 20 minutes I then told a triage agent about the problem. He offered minimal solutions (restore FCP and my libraries from Time Machine backup), then offered to put me through to the Enterprise group. After sitting on hold for another 10 minutes, I got the message that Enterprise was already CLOSED for the day!


Does anyone have any ideas for solutions? I have two major projects that need to be finished and I cannot do anything (and yes, I know I'm an idiot for updating on the first release day!).


Here's a short look at the Crash Log. I cut out the middle section, but can provide more info if anyone wants!:


Process: Final Cut Pro [869]

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

Identifier: com.apple.FinalCut

Version: 10.2 (262455)

Build Info: ProEditor-26245005045000000~1

App Item ID: 424389933

App External ID: 811968672

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Final Cut Pro [869]

User ID: 501



Date/Time: 2015-04-14 21:24:12.168 -0400

OS Version: Mac OS X 10.10.3 (14D131)

Report Version: 11

Anonymous UUID: E2942CF3-9ACA-D7D9-D390-0ADF2E49B953





Time Awake Since Boot: 92 seconds



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



Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000



Application Specific Information:

-[__NSDictionaryI intValue]: unrecognized selector sent to instance 0x608000a6d7c0

abort() called



Application Specific Backtrace 1:

0 CoreFoundation 0x00007fff8c16a03c __exceptionPreprocess + 172

1 libobjc.A.dylib 0x00007fff8be1976e objc_exception_throw + 43

2 CoreFoundation 0x00007fff8c16d0ad -[NSObject(NSObject) doesNotRecognizeSelector:] + 205

3 CoreFoundation 0x00007fff8c0b2e24 ___forwarding___ + 1028

4 CoreFoundation 0x00007fff8c0b2998 _CF_forwarding_prep_0 + 120

5 Flexo 0x00000001041b31ae -[FFMediaEventController _updateModifiedMediaRep:returnIsIncompatibleOriginal:] + 3886

6 Flexo 0x00000001041b47b3 -[FFMediaEventController _syncMediaCompleted:] + 883

7 Foundation 0x00007fff9551ed00 __NSThreadPerformPerform + 293

8 CoreFoundation 0x00007fff8c086a01 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17

9 CoreFoundation 0x00007fff8c078c5c __CFRunLoopDoSources0 + 476

10 CoreFoundation 0x00007fff8c0781bf __CFRunLoopRun + 927

11 CoreFoundation 0x00007fff8c077bd8 CFRunLoopRunSpecific + 296

12 HIToolbox 0x00007fff8da4456f RunCurrentEventLoopInMode + 235

13 HIToolbox 0x00007fff8da442ea ReceiveNextEventCommon + 431

14 HIToolbox 0x00007fff8da4412b _BlockUntilNextEventMatchingListInModeWithFilter + 71

15 AppKit 0x00007fff9374b9bb _DPSNextEvent + 978

16 AppKit 0x00007fff9374af68 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346

17 AppKit 0x00007fff93740bf3 -[NSApplication run] + 594

18 ProKit 0x00000001039a142f NSProApplicationMain + 329

19 Final Cut Pro 0x000000010355ce50 main + 1344

20 libdyld.dylib 0x00007fff95a455c9 start + 1



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

0 libsystem_kernel.dylib 0x00007fff8bbdf286 __pthread_kill + 10

1 libsystem_c.dylib 0x00007fff8832bb53 abort + 129

2 com.apple.Flexo 0x0000000104784be2 FFApplicationHandleExceptionThatShouldNotBeIgnored + 498

3 com.apple.AppKit 0x00007fff93740d1c -[NSApplication run] + 891

4 com.apple.prokit 0x00000001039a142f NSProApplicationMain + 329

5 com.apple.FinalCut 0x000000010355ce50 main + 1344

6 libdyld.dylib 0x00007fff95a455c9 start + 1


[[[[ middle of long log file removed ]]]]]



Model: MacBookPro9,1, BootROM MBP91.00D3.B08, 4 processors, Intel Core i7, 2.7 GHz, 16 GB, SMC 2.1f175

Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In

Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB

Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x85F7, 0x483634314755393747313630304700000000

Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x85F7, 0x483634314755393747313630304700000000

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (7.15.166.24.3)

Bluetooth: Version 4.3.4f4 15601, 3 services, 27 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en1

Serial ATA Device: OWC Mercury Electra 6G SSD, 960.2 GB

Serial ATA Device: HL-DT-ST DVDRW GS31N

USB Device: Backup+ BK

USB Device: Hub

USB Device: FaceTime HD Camera (Built-in)

USB Device: Hub

USB Device: Hub

USB Device: Apple Internal Keyboard / Trackpad

USB Device: BRCM20702 Hub

USB Device: Bluetooth USB Host Controller

USB Device: IR Receiver

Thunderbolt Bus: MacBook Pro, Apple Inc., 25.1

MacBook Pro, OS X Yosemite (10.10.3)

Posted on Apr 14, 2015 6:32 PM

Reply
25 replies

May 11, 2015 1:05 PM in response to Also Zarathustra

Short update on my original problem... and what appears to be (at least for me) the solution.


Over the course of 3 days with Apple on the phone, I recovered my previous versions of FCP libraries from the folder; Movies > Final Cut Backups > "my drive name" Projects and Events > [Select a library that was backed up some days before the problem]


From here, I restored an old version of FCP 10.1.4 (from Time Machine) and then re-opened my "backup" library copy.


At this point, I had to Relink all of my media from the upgraded (but refusing to open) New Library, and here is where I discovered that FCP either corrupted some of my Clips, OR that FCP 10.2 is not nearly as tollerant as 10.1.4.


I was lucky that the clips that could not be relinked were of no consequence, so I went through the painstaking process of re-linking all of the files I could. THEN, with the new library "clean" of these bad files that could not be Linked, I zipped up the 10.1.4 FCP version, and unzipped the 10.2 version (which I had actually put on the desktop and zipped so it would not get in the way).


Finally, I launched FCP 10.2 holding down the Option key, selected my "new" library (the one restored from backup, but without all the nad Linked files), and crossed my fingers. It worked!


I opened and closed the library a few times (and I will keep the old one around a little while just in case)... so I then Consolodated all of my media files back into the New Library, and tomorrow, I will re-enable FXFactory and be back in business!


REMEMBER: you HAVE a recent backup of FCP Libraries automatically created by FCP! You do NOT need to resort to Time Machine for the libraries (and since they can be huge, this is a big time saving).

The Backups are in: Movies > Final Cut Backups > "my drive name" Projects and Events > [Select a library that was backed up some days before the problem] I would suggest restoring the library to your Movies folder, and pulling a version of FCP 10.1.4 from Time Machine... then diagnose the library and see if you're having the same problems!


Good luck!!

May 6, 2015 11:15 AM in response to tobycool

After moving my fonts and still having problems, my issue was resolved by going back to my Time Machine version 10.1.4, as Eli mentioned, opening the problem library, then going through it and deleting all missing media and removing audio files that were missing so that the little yellow triangle disappeared from all the events in the Library. I was then able to open the Library in 10.2 with no problems.

May 9, 2015 8:05 PM in response to Eli Sherer

I had the same issue. It was resolved with the help of a very good Apple tech.


What we did was open Font Book, select all of the fonts, and then perform a font validation (Validate Font from the File menu).


Doing that generated a list of suspect fonts (yellow alert) and bad fonts (red alert). We first pulled the "red" fonts off to a folder on the desktop. When that didn't correct the problem, we did the same with the "yellow" fonts. That corrected the problem. I was then able to launch Final Cut and have the libraries update perfectly.


I subsequently trashed the bad fonts and will add back the suspect fonts if and when I need them. Adding them back one-by-one will allow me to see which one (or ones) was/were causing the problem.

May 11, 2015 2:55 PM in response to Eli Sherer

So...weird thing here. I was having this issue like everyone else. I went through and deleted suspicious fonts, at least the ones that FontBook would let me delete and nothing happened. So I decided to look through my Time Machine backup and went back to the applications folder where the previous version of FCPX was. 10.1.4 I believe. So I clicked restore, and it started to copy, I clicked "Keep Both" and it made a copy. So now I had two copies of the FCPX app in my applications folder. I went to open the project that I was having trouble with on the old version of FCPX, and it said" This library was created with a newer version of FCPX. It will be ignored". So I thought, "Well suck." I figured I would try, yet again, to open the project with the newer version of FCPX, and to my surprise, the problem library opened! I have been trying for weeks now!!!


I'm still not sure what happened, but it worked.


I hope this can help someone else!!!

Upgraded to FCP 10.2, but cannot update library (crashes)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.