FCP X v10.1.1 crashes when opening a Library

Question

FCP X v10.1.1 crashes when opening a Library

I replied to another thread, but then realized that while it was the same error, the stack trace was very different for me and the crash was happening at a completely different spot (and a different time).

There's a particular Library (500G, 5 "events" each with about 50G of original media plus another 50G of proxy media) which, as soon as I attempt to open it, produces the following (truncated to only show the top detail and stack trace; let me know if the whole thing would be of any value).

The other thread mentioned that there might be an issue with Digital Rebellion products. I don't have any; in fact there are no non-Apple components. The projects do reference custom Motion 5 effects.

If any suggestions exist to recover any or all of this, I would be greatly relieved. I've already lost so much work with FCP X since the introduction of Libraries it makes me want to weep...

Thanks for reading!

Process: Final Cut Pro [990]

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

Identifier: com.apple.FinalCut

Version: 10.1.1 (240682)

Build Info: ProEditor-24068002033000000~1

App Item ID: 424389933

App External ID: 299842652

Code Type: X86-64 (Native)

Parent Process: launchd [173]

Responsible: Final Cut Pro [990]

User ID: 501

Date/Time: 2014-04-16 17:30:29.601 -0400

OS Version: Mac OS X 10.9.2 (13C64)

Report Version: 11

Anonymous UUID: CEF2206F-F610-682E-EA3B-A0BD12E0CB8F

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: EXC_I386_GPFLT

Application Specific Information:

objc_msgSend() selector name: countByEnumeratingWithState:objects:count:

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

0 libobjc.A.dylib 0x00007fff946ff097 objc_msgSend + 23

1 com.apple.Flexo 0x0000000109930bf0 +[FFLibrary replicateOfflineMediaWithNewLibrary:] + 2288

2 com.apple.Flexo 0x0000000109920d56 -[FFLibraryDocument initWithURL:isTemporary:createDefaultEvent:error:] + 1414

3 com.apple.Flexo 0x0000000109920e19 -[FFLibraryDocument initWithContentsOfURL:ofType:error:] + 121

4 com.apple.AppKit 0x00007fff8bf68fcb -[NSDocumentController makeDocumentWithContentsOfURL:ofType:error:] + 772

5 com.apple.AppKit 0x00007fff8bf76bb2 -[NSDocumentController(NSDeprecated) openDocumentWithContentsOfURL:display:error:] + 820

6 com.apple.LunaKit 0x000000010ab52967 -[LKDocumentController openDocumentWithContentsOfURL:display:error:] + 39

7 com.apple.FinalCut 0x000000010873e2a7 -[PEDocumentController openDocumentWithContentsOfURL:display:error:] + 471

8 com.apple.Flexo 0x00000001099de573 +[FFLibraryManagerPanelController openLibraries:windowTextMessage:windowDescriptionMessage:error:] + 771

9 com.apple.Flexo 0x0000000109aa05a9 -[FFWorkspace restoreDocuments:urls:] + 713

10 com.apple.AppKit 0x00007fff8bcd7340 -[NSApplication sendAction:to:from:] + 327

11 com.apple.prokit 0x0000000108a537c6 -[NSProApplication sendAction:to:from:] + 101

12 com.apple.Flexo 0x000000010900b3f8 -[FFApplication sendAction:to:from:] + 328

13 com.apple.AppKit 0x00007fff8bcf22a8 -[NSMenuItem _corePerformAction] + 394

14 com.apple.AppKit 0x00007fff8bcf1fe4 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 117

15 com.apple.AppKit 0x00007fff8bd4148d -[NSMenu _internalPerformActionForItemAtIndex:] + 35

16 com.apple.AppKit 0x00007fff8bd41309 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 104

17 com.apple.AppKit 0x00007fff8bce80d6 NSSLMMenuEventHandler + 716

18 com.apple.HIToolbox 0x00007fff9571a1d4 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 892

19 com.apple.HIToolbox 0x00007fff95719787 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 385

20 com.apple.HIToolbox 0x00007fff9572d880 SendEventToEventTarget + 40

21 com.apple.HIToolbox 0x00007fff95763640 SendHICommandEvent(unsigned int, HICommand const*, unsigned int, unsigned int, unsigned char, void const*, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 420

22 com.apple.HIToolbox 0x00007fff95796238 SendMenuCommandWithContextAndModifiers + 59

23 com.apple.HIToolbox 0x00007fff957961e0 SendMenuItemSelectedEvent + 178

24 com.apple.HIToolbox 0x00007fff957960bf FinishMenuSelection(SelectionData*, MenuResult*, MenuResult*) + 94

25 com.apple.HIToolbox 0x00007fff9579e095 MenuSelectCore(MenuData*, Point, double, unsigned int, OpaqueMenuRef**, unsigned short*) + 718

26 com.apple.HIToolbox 0x00007fff9579dcc1 _HandleMenuSelection2 + 446

27 com.apple.AppKit 0x00007fff8bc5a73c _NSHandleCarbonMenuEvent + 284

28 com.apple.AppKit 0x00007fff8bab96be _DPSNextEvent + 2170

29 com.apple.AppKit 0x00007fff8bab8a2b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122

30 com.apple.AppKit 0x00007fff8baacb2c -[NSApplication run] + 553

31 com.apple.prokit 0x0000000108a54f6a NSProApplicationMain + 333

32 libdyld.dylib 0x00007fff9132a5fd start + 1

Final Cut Pro X, OS X Mavericks (10.9.2)

Posted on Apr 16, 2014 2:59 PM

Reply

Answer 1

Apr 16, 2014 3:25 PM in response to Casual Pixels

More info

I created a new Library. Created 6 new events inside the new Library and named each one identically to the event in the Library which wouldn't open.

Replaced the six directories with the directories from the corrupted Library.

Good news; they open. Bad news. The projects are not recognized as projects and appear in the list of clips with a mini yellow Alert ! tag. If I click on it, FCPX thinks it's a missing clip.

So how do I get FCP X to recognize it as a project or otherwise get it to do the automatic version management it obviously didn't get right the first time?

Reply

Answer 2

Apr 16, 2014 5:27 PM in response to Casual Pixels

Casual Pixels wrote:

The other thread mentioned that there might be an issue with Digital Rebellion products. I don't have any; in fact there are no non-Apple components. The projects do reference custom Motion 5 effects.

Just to clarify, in the previous thread the problem was fixed by a Digital Rebellion product, it did not cause it.

Reply

Answer 3

Russ H

Level 7

22,432 points

Apr 16, 2014 6:58 PM in response to Jon Chappell

Jon Chappell wrote:

Just to clarify, in the previous thread the problem was fixed by a Digital Rebellion product, it did not cause it.

And this thread…

Russ

Reply

Answer 4

Apr 16, 2014 7:16 PM in response to Jon Chappell

I don't believe this is a preference/settings issue.

Here, it's the FCPX has some problem with converting Libraries to 10.1.1, specifically the CurrentVersion.flexolibrary file.

This Library was working fine the last time I opened it; I'm not exactly sure which version it was but something prior to 10.1.1.

Now, it fails to open the library at all. By creating a new library and trojan horsing the individual events into that new libary, the events and clips can be seen, though I'm guessing because the Library was created in v10.1.1, the project files don't get to go through an update process and so appear broken to v10.1.1.

As much as I love FCPX when it's working, the testing is obviously way way less than it absolutely needs to be. And stability seems to be getting worse and worse with every release. Since Libraries have been introduced I've lost countless hours of work as projects and libraries go south. Crashes and corrupted data and hours or days torched. It's just staggeringly depressing.

Reply

Answer 5

Apr 16, 2014 7:50 PM in response to Casual Pixels

I did download and try the Digital Rebellion product.

The good news is that after running it and deleting the preferences I was able to open the Library in question (the original version of it; not the one I jury-rigged).

However, FCPX then lauched a background render and it's impossible to kill.

If I bring up the Background Task window, it shows Rendering at 100% and if I twiddle the arrow beside it, it shows a "Background Render" at 0%.

While this is happening, I cannot open anything inside the Library.

After waiting 10 or 15 minutes, I tried to Quit FCPX. No dice. A modal progress bar window with an infinite progress bar and the message "Cancelling background tasks". No sounds of any disk I/O.

This review on the Digital Rebellion side made me crings: "I do want to point out two applications I use the most...Preference Manager and FCS Remover. And how would you like to hear that Apple employees, people who work on Final Cut Studio, use these applications themselves, all the time? Yeah, that inspires confidence in the power of these tools."

Forget the confidence it inspires in the tool; what does it say about the confidence it inspires in the product that needs that kind of constant intervention?

Anyway, thanks for the pointer and correction about the DR stuff. I'm burnt out and stressed that this is all lost. I'll give it another whirl tomorrow.

Reply

Answer 6

Apr 17, 2014 6:30 AM in response to Casual Pixels

Casual Pixels wrote:

Forget the confidence it inspires in the tool; what does it say about the confidence it inspires in the product that needs that kind of constant intervention?

To be fair, it supports multiple NLEs which all have all have their own issues, although I would say that FCPX seems to have project corruption problems far more often than other apps.

Reply

Answer 7

Apr 17, 2014 7:27 AM in response to Jon Chappell

I don't disagree, but I repeatedly find myself spend vast amounts of time trying to recover from corruption problems and as often as not having to redo all my work anyway when that effort proved fruitless.

I love this product when it works, but I don't know that I can continue take that amount of overhead.

And what makes it worse is that I find there's simply nothing more soul-crushing than having to re-do work you thought was done and that you were totally happy with.

I like the idea of Libraries, but given the option between that and having them instead spend that time and effort on stability and reliabilty issues, there's absolutely no question which one would have made the most difference in my life.

Anyway, while the projects were lost, a whole mess of Multicam work was recovered by the DR tool so your clarification on what the other thread was saying is very appreciated.

Reply