FinalCutPro 10.5.3 Crashes on Exporting Any File

Finally, a fix is out. On Apple website, it says...

New in Final Cut Pro 10.5.4

Released July 8, 2021

• Improves stability when exporting with certain macOS Language & Region preferences.
• Improves stability when playing H.264 or HEVC media.

That's it. This is a solving.

More on investigation, found from other user.

M1 Version

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x000049a9806b1edc

Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11

Termination Reason: Namespace SIGNAL, Code 0xb

Terminating Process: exc handler [887]

VM Regions Near 0x49a9806b1edc:

GPU Carveout (reserved) 1000000000-7000000000 [384.0G] ---/--- SM=NUL reserved VM address space (unallocated)

-->

MALLOC_NANO 600000000000-600008000000 [128.0M] rw-/rwx SM=PRV

Intel Version (Mine)

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x00002587beec07d0

Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11

Termination Reason: Namespace SIGNAL, Code 0xb

Terminating Process: exc handler [1007]

VM Regions Near 0x2587beec07d0:

SQLite page cache 13b0b1000-13b0c1000 [ 64K] rw-/rwx SM=PRV

-->

MALLOC_NANO 600000000000-600008000000 [128.0M] rw-/rwx SM=SHM

Exact same Exception Codes points to memory access error. Same command MALLOC_NANO and same memory address 600000000000-600008000000 [128.0M]. This error happens on only 16GB machine (As far I have seen).

If you have this same issue please share a crash log to help narrowing down.

Right now, I am pretty sure this issue occurs only on 16GB RAM system based on my finding. Low disk space is not likely to be the cause too since other systems have around 30GB whereas mine has 200GB, both crashed. Also, CPU architecture is not be the cause since it happens on both x64 and ARM64 as well as GPU since both MacBook Pro 16 (Dedicated AMD Graphic) and my MacBook Air 2020 (Integrated Intel Iris Graphic) have the same problem.

I am really wondering what causing this because my machine (apart from hardware perspective) is clean. I have a clean install macOS with FCP and compressor right from App Store, no others. So nothing seems to be able to mess up with this crash.

No, it is a fresh start. Started over from the welcome screen, newly created user, no migration. Library/Project gets automatically created on first FCP launch. Even weirder is that FCP crashes on nothing applied to a clip, just import and click export right away. This made me believe that a problem comes from FCP itself.

Also have seen that some users can get away by exporting a non-audio clip which I planned to try too. I will get back on this later.

It actually happens at the same place, when I say crash on exporting meaning it crashes when Save button is clicked/pressed (in my case using return key, also mentioned at the begin of this thread). Anyway, appreciated for your input.

Also, tried exporting video only using Export File (default) option which renders ProRes 422 LT - crashed. But the only thing that does not make FCP crash is detaching audio from clip and removed it before hit export because choosing export video only did not solve. I think when other report that export video without audio helps, they mean remove audio from a timeline not from choosing an export option.

At the end (for now), seems like problem is not really hardware-specific.

Thanks terryb, I do not disagree about third party software but I am quite confident about software conflicting is not an issue because I started everything over from zero without any addition software or migration (including first-party ones except compressor).

Uninstalled Compressor, still crashes on video with audio. Only have Final Cut Pro app. It is really FCP internal bug which effecting some (including myself) but definitely not all.