FCPX crashes - regardless of which Library.

Hey Folks!
I'm just wondering if anyone else has seen FCPX not able to stay open. A somewhat embarrassing thing happened last night. during the Superbowl a bunch of us editors were all talking NLEs and I was talking about how great FCPX is. So, after the Superbowl we went to my edit suite and I could not get any of my projects to stay open. No matter which library I opened they would crash within a minute or two. Argh!

This is the latest system OS and the latest version of FCPX on a new MAC Pro trashcan and no other applications running. Later when I get back in the editing room I will try opening them in a different user and see what is up. It is so strange.

You might be able to get a clue as to what's going on by looking at the crash log. Open the Console app, and twirl down the User Diagnostic Reprts section in the sidebar. Find a FCP .crash log with a timestamp you know is one of the ones you saw. select it and look for a couple lines at the top like this:

"
(some info, then..)

PlugIn Path: /Library/Plug-ins/*/motionVFXmFlare
PlugIn Identifier: com.motionVFX.FxPlugGenerator.mFlare64
PlugIn Version: 1.5.2 (320)

(more info, and then...)

Crashed Thread: 52 BGTask: FFEffectLibraryThumbnailRequestManager Dispatch queue: NSOperationQueue 0x618008c3fe20 :: NSOperation 0x618005154110 (QOS: USER_INITIATED)

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000001d6331fe4

(or just something like the following...)

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000000a0

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

It may tell you if it's a bad plugin or effect or something. If not, post back and someone can suggest some other steps I'm sure.

If you use shared media (not in the library) you can try un-mounting the media drives and opening a library. if it's a corrupt clip, it should open fine as it'll be offline. If that's the case then you'll need to track down the corrupt bit, but see if it's a plugin or something first...

Well, I am in the process of giving it another go. The computer rested and upon re-boot so far things are working as expected..... :silly:
I hope this continues. I will let you know if it happens again during this session and look at the logs as soon as I get a chance.

Thanks for responding so quickly

So, two days of revisiting the various timelines and so far so good. No problems. Whew! :kiss: