Level 1

21 points

FinalCutPro 10.5.3 Crashes on Exporting Any File

When hitting Next... and Save on Export dialog, FCP just simply crashes. A few moment system dialog shows up "Final Cut Pro Quit Unexpectedly".

I have tried these :

Reinstall FCP
Delete All Libraries
Reset Preference
Try export few codecs - HEVC (either mov and mp4) and ProRes 422 LT
Try few bunch of vdo files

None could solve. Anybody has the same issue here ? Did not have this issue before 10.5.3.

Intel MacBook Air 2020, Big Sur 11.4, FCP 10.5.3, Compressor 4.5.3

Posted on Jun 21, 2021 1:24 AM

Top-ranking reply

GoLfWRC Author

Level 1

21 points

Posted on Jun 21, 2021 11:44 PM

For those who are not be able to solve this issue, based on other user who has contacted Apple, looks like we will have to wait for an update for this. But if you have a backup of previous FCP. I suggest to roll it back right now since it would work perfectly. According to nahumyamin.

"[UPDATE]

I've reverted to the previous working version of FCP (10.5.2) from my time machine backup, and no issue with exporting. The application works as expected and in the same way as before.

I suspect there is an issue with the new released version, I will keep this previous version and wait to see if there is an update or fix from Apple."

Hope this also helps you.

View in context

Similar questions

80 replies

GoLfWRC Author

Level 1

21 points

Jun 21, 2021 11:47 AM in response to Tom Wolsky

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.

Tom Wolsky

Level 10

152,815 points

Jun 21, 2021 11:03 AM in response to GoLfWRC

Did you do any migration, user or anything else, during or after?

Can you export a project without audio?

reham199

Level 1

4 points

Jun 22, 2021 9:41 AM in response to GoLfWRC

changed region to us

Tom Wolsky

Level 10

152,815 points

Jun 28, 2021 1:47 AM in response to jasonnPOS

Did you see the Language region to US? Try that.

Jun 21, 2021 1:33 AM in response to GoLfWRC

Please run Etrecheck and post its full report here. Use the "additional text" button and paste the report into the text box.

As you may see in other threads, a number of people, but certainly not everyone, have had issues.

GoLfWRC Author

Level 1

21 points

Jun 21, 2021 2:12 AM in response to GoLfWRC

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.

Jun 25, 2021 3:30 AM in response to GoLfWRC

Just to confirm that my Language is English (UK) and my Region is United Kingdom and I have no problems exporting.

I do not understand why you have not used Etrecheck. It will do no harm and in 5 minutes from reading this you could have a report which may (or may not) point to a solution.

It's the equivalent of going to a doctor with a baffling chest problem but refusing to have a scan!

GoLfWRC Author

Level 1

21 points

Jun 23, 2021 3:40 AM in response to GoLfWRC

ake.k

Julioaa

Thanks for info.

Don't know which more regions got effected from this issue but changing it to US seems to be the top cure.

Tom Wolsky

Level 10

152,815 points

Jun 21, 2021 12:54 PM in response to nicolle_zm

Someone reported removing additional language fixed their problem. There may be multiple causes of course or something specific in your case. A lot of people are looking at it but no positive solution has come up for those who have the problem.

GoLfWRC Author

Level 1

21 points

Jun 27, 2021 11:38 PM in response to GoLfWRC

More confirmation on this, I just have a chance to access my another Thailand-Region big sur 11.4 mac with some other softwares installed. But this one has FCP 10.5.2 (prior to a broken one), it does not crash or anything. Isn't that obvious ?

terryb

Level 4

3,430 points

Jun 21, 2021 11:47 AM in response to GoLfWRC

An Etrecheck report would be very useful to help you troubleshoot. Without it there's lots of guessing and assumptions that might not be correct.

Tom Wolsky

Level 10

152,815 points

Jun 23, 2021 5:37 AM in response to Meyao

The interim solution is right in this thread. Reset language and region. Follow the directions above.

Tom Wolsky

Level 10

152,815 points

Jun 23, 2021 4:06 PM in response to ZviadPochkhua

In Language System Preferences set the Region to US.

GoLfWRC Author

Level 1

21 points

Jun 21, 2021 10:14 AM in response to GoLfWRC

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.

terryb

Level 4

3,430 points

Jun 21, 2021 12:31 PM in response to GoLfWRC

I understand, but we've seen people who say they've done a clean install but when we see the Etrecheck report we find they actually haven't, or they migrated user space data, not just applications. Not saying this is the case with your machine, but sometimes there's vocabulary used that doesn't match what has been done which can lead to unnecessary or down-the-wrong-path troubleshooting suggestions. Easier to look at a standard data report which removes much of the potential vocabulary ambiguity.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

FinalCutPro 10.5.3 Crashes on Exporting Any File