Final Cut Pro keeps crashing moments after startup

Question

Level 1

5 points

Final Cut Pro keeps crashing moments after startup

Hey! So for the past week and a half, Final Cut has consistently kept crashing seconds after I boot it up. The time it’s open for before crashing does vary but it’s usually only open for a good few seconds. I’ve tried many different ways to potentially fix it, like updating the app/OS, uninstalling & reinstalling, deleting Generated Library Files, running First Aid, looking through multiple forums and websites and nothing has been successful (aside from maybe making boot up faster? Still crashes)

Every time I’ve gotten the same problem report but I’m not knowledgeable enough on stuff like this so I can’t figure out exactly what the issue is, I’ve left the problem details copy and pasted with a screenshot of the report too. I’d really like to figure out what’s going on since I’ve got a lot of projects to work on but it’s basically impossible to do in this state, so any help/feedback would be greatly appreciated!

Process: Final Cut Pro [879]

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

Identifier: com.apple.FinalCut

Version: 10.6.5 (405627)

Build Info: ProEditor-40560027015000000~4 (18H41)

App Item ID: 424389933

App External ID: 852712461

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Final Cut Pro [879]

User ID: 501

Date/Time: 2024-01-19 23:30:04.651 +0000

OS Version: macOS 11.7.10 (20G1427)

Report Version: 12

Anonymous UUID: D78EC9F4-DF69-9F79-ACC1-4CC62F1992D4

Sleep/Wake UUID: 0637C0DE-4186-4D0A-89F7-1C77C7EA1697

Time Awake Since Boot: 2400 seconds

Time Since Wake: 1400 seconds

System Integrity Protection: enabled

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

Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:

Last ProCore Log: assertion failed: FFVideoProps must have a numeric sampleDur & frameDur (((Boolean)(((_sampleDuration).flags & (kCMTimeFlags_Valid | kCMTimeFlags_ImpliedValueFlagsMask)) == kCMTimeFlags_Valid)) && ((Boolean)(((_frameDuration).flags & kCMTimeFlags_Valid) != 0))) :: -[FFVideoProps _validateVideoProps] (file: /Library/Caches/com.apple.xbs/Sources/Flexo/Flexo-40560.12.15/framework/providers/FFVideoFormat.mm, line: 1899)

FFAnchoredCollection setClippedRange:

-[FFAnchoredCollection setClippedRange:], FFAnchoredObject.m:3183

abort() called

iMac 27″, macOS 11.7

Posted on Jan 19, 2024 3:58 PM

Reply

Answer 1

Top-ranking reply

Ian R. Brown

Level 7

24,164 points

Jan 20, 2024 9:47 AM in response to LochlinBlue

There could be a problem with your current Library/project.

Change its name in the finder so that FCP will not recognise it and launch FCP again whilst trashing the preferences.

Does FCP stay open? If so, create a new Library and add some clips and a new test project to it.

If it works OK it would suggest that the problem lies in your original Library.

Reply

Answer 2

BenB

Level 6

13,198 points

Jan 20, 2024 9:09 AM in response to LochlinBlue

Delete all render files, too. I'd delete all cache files (with FCP Library Manager).

Reply

Answer 3

terryb

Level 4

3,376 points

Jan 19, 2024 5:09 PM in response to LochlinBlue

Usually the first thing to try is to delete FCP Preferences. Hold Option and Command while launching FCP and choose Delete Preferences. It will open the default Untitled library. Re-open the library you were working on, set the Preferences back to the way you like them (disable background rendering, reset Import to Leave Files in Place, etc.) and see if the issue has been resolved.

If that doesn't help, post an https://etrecheck.com report here using the "Additional text" button below in your reply.

Reply

Answer 4

LochlinBlue Author

Level 1

5 points

Jan 24, 2024 2:03 PM in response to Ian R. Brown

I think you’re right! Created a whole new library and everything was working fine, whereas when I go on my original one is struggles to load and eventually crashes. If I were to guess what the issue is, it’s probably because there’s a lot of unneeded media in there that causes it to take up a lot of memory, since it is due a clean up.

Reply

Answer 5

Tom Wolsky

Level 10

152,780 points

Jan 20, 2024 9:22 AM in response to LochlinBlue

Your system has likely been fubared by CleanMyMac. You should do a full backup or clone of the drive, a clean system install, migrate users only, and reinstall your apps.

Reply

Answer 6

Jan 25, 2024 3:59 AM in response to LochlinBlue

It may not be the size of the library per se as it's also possible there could be a corrupt clip creating chaos.

Reply

Answer 7

Jun 7, 2024 2:08 AM in response to ornina193

Projects are kept in Libraries which are completely separate from the FCP app so you should be able to double-click the Library and have it open in the repaired FCP.

Reply

Answer 8

LochlinBlue Author

Level 1

5 points

Jan 20, 2024 7:09 AM in response to terryb

Thank you for the reply!

Report

Unfortunately, deleting my preferences didn’t seem to solve anything, just crashed again before I could change my preferences back to what I had. I do have a EtreCheck report that I’ll put here, hopefully this helps narrow the problem down!

Reply

Answer 9

Jun 6, 2024 6:59 PM in response to LochlinBlue

Does anyone have a way to retrieve projects already edited after fixing FCP? I spent hours on a video and I really don't want to repeat the editing process T-T

Reply

Final Cut Pro keeps crashing moments after startup

Similar questions