Crashes when export

Hi!

Im driving crazy. I'm trying to make a export by master file and FCPX crashes immediatly, no warning nothing. It doesnt matter which project i have opened, it happens with all. And also the other export methods..

Im running an old version 10.1.2 on an old Imac 2011.

I tried already delete preferences, quit chrome, any other library. Nothing works.

I hope someone can help me!

Thanks very much.

We are starting to see several reports of old versions of FCPX running on older machines and older versions of MacOS crashing during export. This implies something has changed - maybe some kind of software update which is causing this.

One person tracked his particular case to an update in /System/Library/PrivateFrameworks/MobileDevice.framework

See the below discussion thread. If you have a backup you could try restoring that file to an older version. Whether it fixes it or not, please post your results here.

www.fcp.co/forum/4-final-cut-pro-x-fcpx/...px-crashes-on-export

Also do all the regular troubleshooting steps such as ensure you have at least 15% free space on all drives, run Disk Utility First Aid on all drives (which requires being in Recovery Mode for the system drive), verify all drives are HFS+ not ExFAT, etc. support.apple.com/en-us/HT201314

Although you quit Chrome, I personally would not have Chrome on any Mac I'm using FCPX on. See the recent post by FCPX.guru, one of our most experienced people: www.fcp.co/forum/4-final-cut-pro-x-fcpx/...le-chrome-true-story

Last year a Chrome update rendered many Macs non-bootable. This halted production of various TV shows which were using Avid: arstechnica.com/information-technology/2...d-macs-from-booting/

Running Disk Utilitie's First Aid on the system drive does not require booting into Recovery Mode. I've always done it monthly, and it always ran just fine. Mojave now warns you that the whole system will stop responding while it is running. But I don't ever recall having to do that ever. If it was required back then, well, I sure didn't notice it required it. Are you sure about Recovery Mode?

FCPX.guru wrote: Running Disk Utilitie's First Aid on the system drive does not require booting into Recovery Mode. I've always done it monthly, and it always ran just fine...

It will both run and fix problems without Recovery Mode on a non-system volume.

On the system or boot volume, it will *run* just fine without being in Recovery Mode, but if it finds anything it can't be fixed unless it's in that mode. I think that's why Apple's docs state use Recovery Mode if running it on a system volume: support.apple.com/guide/disk-utility/rep...evice-dskutl1040/mac

I had a discussion with MacOS escalation support about this and they confirmed Recovery Mode should be used on the system volume. I asked why isn't that documented and they said it is -- see the above article. I told them this hardly constitutes operational documentation since nobody knows this. They said that's too bad.

Edit/add: First Aid just runs fsck, and if run on the system volume it uses the -n -l options, which means "verify only" and "lock the volume". I guess if you trust 100% of the fsck output and examine it closely then if you see a problem you could run it from Recovery Mode or Single User mode so it could then fix the problems. In this case the OP is on an old version of MacOS and there were often HFS permissions problems which Disk Utility would fix. I cannot remember of those were always listed in the output.

More info on fsck, esp. regarding APFS: eclecticlight.co/2019/09/30/should-you-t...s-first-aid-or-fsck/

As a former UNIX guy, FSCK in a real UNIX system runs on system drives just fine without any tricks. Apple must have something going on to require using the repair partition. I tell you what I REALLY miss since First Aid rarely fixes anything of significance, DiskWarrior. I've saved lives with that app numerous times. But, Apple seems to have put the squash on that amazing app, too.