- June 3, 2021 at 7:34 pm
Starting a couple days ago, a certain large Library always crashes a
few seconds after I try to open it.
I have reset preferences in FCP – still crashes.
I have tried opening some of the backups of this same Library, created a
few weeks ago – they also crash.
Totally different Libraries, on the same external hard drive, don’t
Any idea what’s going on? Could this happen because a video clip
imported into the Library has been corrupted?
I read in another place, that after I “show package contents”, I should
try taking most events out of the Library, and putting them into the
trash. Then adding them back one by one – maybe one of the events is
corrupted? Should I try to do this? Does this make sense?
Thanks for any helpful suggestions!
- June 4, 2021 at 12:17 pm
Sorry to hear this. Normally FCP data integrity is excellent, esp. on directly-attached hard drives which are formatted APFS or Mac OS Extended Journaled (HFS+).
First make sure you have at least 20% free space on all drives. Then run Disk Utility First Aid on all drives to make sure there’s no filesystem problem.
The fact that weeks-old library backups also crash may imply a system-level problem, or plugin issue, not corruption in your current library.
A common cause of FCP crashes (but not necessarily data corruption) is 3rd-party plugins. Can you examine any 3rd-party plugins and remove or update them? Plugins often have an external deinstallation procedure or the plugin developer publishes methods to manually deinstall them.
Don’t mess around inside your library unless you have a complete backup of it.
One relatively safe thing is delete all render files. You can (carefully) do that in Finder by deleting the library folders named Render Files. However there is a 3rd-party utility which safely does that called Final Cut Library Manager: https://www.arcticwhiteness.com/finalcutlibrarymanager/
After doing all of the above, if it still crashes, if you post the crash log I will examine it. Please post it as an attached text file, not an in-line post.
Application crash logs can be found by holding the OPT key in Finder and selecting menu Go>Library>Logs>Diagnostic Reports.
Please also state the year and model of your Mac and what version of MacOS and FCP you are running, also the make and model of the external drive and while filesystem it uses (from Finder Get Info).
- June 4, 2021 at 6:51 pm
This literally just happened to me last week. Large(ish) library crashes on startup, as well as its associated backups. It usually would crash right on load-up, but sometimes it would allow me to make a click or two before it implodes. I trashed preferences, removed recently installed effects and generators, deleted all render files, analysis files, and proxy media. No luck whatsoever. The fact that it is inconsistent in when it decides to crash is interesting. I’ve saved the crash log, would love if you could take a look.
2013 MacPro, 10.15.7 Catalina, FCP 10.5.2, OWC Thunderbolt 2 RAID MacOS Extended (Journaled)
- June 4, 2021 at 9:53 pm
Matt, you already did several good troubleshooting steps. It crashed in the method FFEffectStack due to an unrecognized selector. I think it was technically an Objective-C language exception. The question is what effect was involved. I can’t tell from the crash log. Prior to that it was in the FCP framework “flexo”, which implements several key parts of the app.
Frame 12 and 13 mention the method FFAnchoredSequence, which might be a secondary storyline.
Toward the end of the crash log is the section called binary images. That lists all code loaded in the process at the time of crash. There was code from several plugins loaded into FCP address space. Many FCP plugins prior to Big Sur on Apple Silicon run within the address space of the FCP process. That means any bug in any thread of any plugin can crash or destabilize FCP.
That should be improved as developers re-write their plugins using the FxPlug 4 framework, which is mandatory for Apple Silicon. But until then any mysterious crashes where 3rd-party plugins are used require scrutiny of all plugins. Your plugins within FCP’s address space include:
Pixel Film Studios (several different plugins)
Digital Anarchy Flicker Free
I suggest you update all those effects or remove them if needed as part of debugging. CoreMelt plugins can be updated using their installers: https://coremelt.com/pages/downloads
There have been many problems traced to Pixel Film Studio plugins. If possible try removing those or make a test library and copy a project over there, then remove those from that test timeline. Here is how to remove those plugins: https://store.pixelfilmstudios.com/how-to-uninstall-a-plugin/
Digital Anarchy is a good company but they have an updated version of Flicker Free. Make sure you are running the latest version: https://digitalanarchy.com/Flicker/main.html
FxFactory is like an apps store for plugins. The host FxFactory app is frequently updated. Make sure you’re running the latest version.
Even though you didn’t report any MacOS kernel panics, you might want to review what 3rd-party kernel extensions are in use. Those can destabilize or crash MacOS or applications. To inspect this, type this command in terminal:
kextstat | grep -v com.apple
- June 4, 2021 at 10:29 pm
This is all excellent information, Joe – I appreciate the knowledge and time!
Based on the info about the the FFAnchoredSequence I now suspect it may be a PixelFilm effect.. I used an image zoom effect that lives in a title track above the main storyline. Other than that there aren’t any effects applied to the clips themselves, it’s just a large multicam project.
What would be the best method of starting a new library and copying the project/event to it if I can’t keep this original library open for a length of time?
- June 4, 2021 at 10:37 pm
Try to export a full library XML, then create a new library and load that XML.
Log in to reply.