FCPX 10.4.8 running on iMac Pro Mpjave 10.14.6. Ram: 64GB
My FCPX keeps hanging with beachball, virtually on any Library and any project and the only way out is to Force Quit. This happens if I try to move anything within FCPX, like to a new Event, or open a Project.
Thanks for replying. I got 64GB when I ordered my iMac Pro to future proof it, as I am not planning on upgrading hardware for at least 5 years, maybe 10!
I have 1TB internal SSD, with 560GB free.
I looked at Activity Monitor, and and when FCPX freezes (beach ball), it has plenty of resources, and it just stops from running. The cpu for FCPX does not change, neither does the ram usage.
I did a Force Quit and deleted all render files, cache and lock files. This meant I was at least able to start FCPX. I tried opening some Libraries and some open and some freeze as soon as I try to make any changes. I am going through them slowly, and using Final Cut Library Manager to delete all rendered files.
Check your drives... I've had similar hangs with my pegasus (TB2) unit when one of the drives in the raid is approaching its eol. Take a look at the drive logs and see if one of the units isn't timing out and then resetting itself.
When I replaced the drive in my R6 the SBBODs went away.
pszilard wrote: FCPX 10.4.8 running on iMac Pro Mpjave 10.14.6. Ram: 64GB
My FCPX keeps hanging with beachball, virtually on any Library and any project and the only way out is to Force Quit. This happens if I try to move anything within FCPX, like to a new Event, or open a Project....
Make sure you are not running the Chrome browser. It can saturate the VideoToolBox framework causing FCPX to hang or crash.
Try a test with your data and libraries only on a locally-attached drive, not the Synology NAS.
It could also be caused by a plugin.
Due to current limitations in MacOS plugin architecture, a plugin can hang or crash the host app - FCPX in this case. This is because currently all plugins run "in process". With the new FxPlug 4 SDK, it will be possible for developers to migrate their plugins to an "out of process" design which will not crash or hang the host process:
In the current architecture any plugin (excepting those based on a Motion template) can cause this and it is often difficult to determine which one. The more plugins you have the greater the risk.
There should be a totally standardized method to check plugin versions, update them and remove them. Alas, there is not. You might be able to create a new user account, install FCPX in that account, then try one of the "problem" libraries or data sets.
Normally I use Brave browser, which is built on Chrome - so I'll close that before starting FCPX.
Libraries can only run from local drives or SAN, and my Synology is configured as NAS only - so I don't ever run (can't) a Library from there. I do however store Libraries on the Promise box, which is a SAN, but never had problems before.
I will have to do more debugging. ATM I am pre-occupied with setting up clients to work from home, as I am an IT Support person.