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

Question

Level 1

59 points

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: 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

Answer 1

Eli Sherer Author

Level 1

59 points

Apr 15, 2015 4:11 AM in response to Eli Sherer

Short update... I deleted and reinstalled FCP 10.2.

When I launched, FCP created a new Library and that one opened fine. But when I tried to update my old library again manually, the same crash occurred.

So it seems that this has something to do with either the update process, or there's something in my existing library that is causing FCP to crash when trying to open the updated library files.

Will be calling Apple again today... maybe someone else will have some luck based on this info as well.

Reply

Answer 2

Tom Wolsky

Level 10

151,010 points

Apr 15, 2015 6:08 AM in response to Eli Sherer

TThere have been reports of people having problems with corrupt fonts causing library crashes. It probably only happens for fonts used in projects. You might want to check through your font book for anything that looks corrupted, maybe remove any additional fonts as a test.

Reply

Answer 3

Morade77

Level 1

0 points

Apr 15, 2015 6:42 AM in response to Tom Wolsky

Hi all,

I have the same issue. As Tom said. I removed all my user fonts in the finder and then FCP X opened normally. I tried to work with a new library : Ok.

But I tried with an old library and when I wanted to export, it crashes again. It seems to be my 3rd party pluggins ...

Reply

Answer 4

Apr 15, 2015 9:18 AM in response to Morade77

I'm also having issues updating my libraries. A couple updated fine, but then it got stuck on one. When I restore that library from a Time Machine backup, and try again, it always gives me the beach ball, and nothing happens. I have restored pre-upgrade libraries from Time Machine, because I had to force quit the app during the upgrade process, and I don't want to risk corrupt Final Cut libraries.

I will try again now, updating my libraries one by one, and report back. For the record, I don't have any user installed fonts.

Reply

Answer 5

Apr 15, 2015 10:31 AM in response to Eli Sherer

I did the same things and have suffered from the same on one edit system. We have three edits systems all running FCPX. I've upgraded two of them in iMacs 5k Retina systems. They work perfectly. But the third and main edit system is a NEW Mac Pro. All systems are running Yosemite 10.10.3.

On the Mac Pro system, I was getting the same errors you are mentioning with updating and opening previous projects. I, too, was getting the error telling me that I had corrupt fonts and to remove them. Before I started this process, I cloned my hard drive with Carbon Copy Cloner as a safety backup and I'm glad I did. Well... I scanned for corrupted fonts and found four of them, so I removed those fonts using Font Book. I cleaned the system of all clutter, repaired permissions, ran Cocktail to clean a system level, and scanned my drive for errors. NOTHING... Because this is a main edit system and I have to use this now, I restored my hard drive using Carbon Copy Cloner and everything is back to normal except one thing. The App Store will not see FCPX for an update. After the restore, this system is now running FCPX 10.1.4 again and the App Store will not se the update to 10.2 anymore. This is getting to be a real joke here... I've wasted a full day on this mess and I'm nowhere closer to a solution.

Reply

Answer 6

Apr 15, 2015 10:38 AM in response to Wayne Carey

I let the upgrade run without interrupting it, and it upgraded fine, guess I was just too impatient earlier (Activity monitor showed FCPX as not responding, but my external disk was being accessed). Now all my libraries are upgraded and up and running. Running on a 13" Early 2011 MacBook Pro with 16GB RAM. The disk containing my Libraries is a WD MyBook Velociraptor Duo.

Reply

Answer 7

Eli Sherer Author

Level 1

59 points

Apr 15, 2015 11:09 AM in response to moritzhberg

OOk. One note of interst now. The Apple tech checked the full version of my crash log and noted that there's a plugin called "FFMedia plugin" that appears as a problem in the log file.

Problem is: I can't figure out where this plugin is located, or even if that's the actual name of the plugin. Does anyone else have this or have any idea where its from?

Reply

Answer 8

DERMODpl

Level 1

10 points

Apr 15, 2015 1:43 PM in response to Eli Sherer

I have the same problem and I'm not able to solve it. It does not work FCPX and Motion after the update. Tomorrow, it will most likely lose the job. 😟

Reply

Answer 9

Apr 15, 2015 7:26 PM in response to Eli Sherer

I have the same problem. The way I have managed to resolve it was this...:

launch FCP-X while holding Option key - this will open a dialogue where you can select which Library to open - or whether to create a new one.

Select to create a new one (name it "TEMP") - but be quick to do so before the FCP-X crashes. Might need few tries to do this...

Once you have crated the new "TEMP" library - FCP-X will start normally.

Inside FCP-X chose to close the "TEMP" library from the FILE menu.

Then simply chose to open the library that was crashing for you before - you will be prompted to update this library.

But this time the update will work and the library will open...

This worked for me - I hope it helps others...

Totoro

Reply

Answer 10

DERMODpl

Level 1

10 points

Apr 17, 2015 12:56 AM in response to Peter Majtan

Unfortunately, "TEMP" method didnt work for me. Only helped to remove all of the user fonts in font book.

Reply

Answer 11

Apr 17, 2015 6:50 AM in response to Eli Sherer

None of these options worked for me. But.... I did find something very very interesting. All of these crashes are completely related to the graphics card driver itself. I've installed FCPX 10.2 on three computers: 2010 iMac, 2014 iMac 5k Retina, and a 2014 Mac Pro. FCPX 10.2 will ONLY run fine on my 2014 iMac 5k Retina system. The other two computers crash fairly quickly and give me the same error on both (except they have two different graphics cards listed). Here's the error I get on my 2010 iMac using the default Untitled Library with nothing inside (no video clips, audio clips or graphics files - NOTHING):

VM Regions Near 0x1a47a2003:

Image IO 00000001a479f000-00000001a47a2000 [ 12K] rw-/rwx SM=PRV

-->

__TEXT 0000123480000000-000012348029b000 [ 2668K] r-x/rwx SM=COW /System/Library/Extensions/AMDRadeonX3000GLDriver.bundle/Contents/MacOS/AMDRade onX3000GLDriver

Now, the only difference for the Mac Pro is the graphics driver file is different but its the same error. This is very very disappointing...

Reply

Answer 12

Tom Wolsky

Level 10

151,010 points

Apr 17, 2015 6:58 AM in response to Wayne Carey

And the graphics cards are and how much VRAM?

Reply

Answer 13

Apr 17, 2015 7:09 AM in response to Tom Wolsky

They are as follows:

2014 Mac Pro: Dual AMD FirePro D700 6144 MB

2010 iMac: AMD Radeon HD 6970M 2048 MB

And the one that works fine....

2014 iMac 5K Retina: AMD Radeon R9 M290X 2048 MB

I have no explanation for why this is occurring, even after the Supplemental Update for the graphics cards posted yesterday.

Reply

Answer 14

Apr 20, 2015 1:22 PM in response to moritzhberg

Similar experience here.

Reply

Answer 15

Apr 20, 2015 1:28 PM in response to Eli Sherer

Here's what I've found out. It IS font related. If you remove ALL of your fonts from the Users/(computer name)/Library/Fonts folder and copy them to your desktop, it will work just fine. Some font on your system is causing this issue. We got our main edit system running using ONLY the default system fonts and NO user fonts installed. Kinda ***** but that's the only solution to this MAJOR program bug. It is directly related to the new 3D fonts part of Final Cut Pro X 10.2.

Reply