Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

Final Cut Pro Crashes When I Try To Transcribe Captions


Process: Final Cut Pro [62802]

Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro

Identifier: com.apple.FinalCut

Version: 11.0 (430149)

Build Info: ProEditor-43000139026000000~9 (2E92d)

App Item ID: 424389933

App External ID: 870244110

Code Type: ARM-64 (Native)

Parent Process: launchd [1]

User ID: 501


Date/Time: 2025-07-11 16:02:51.0317 -0700

OS Version: macOS 15.5 (24F74)

Report Version: 12

Anonymous UUID: 7D0459CE-0833-9975-6B89-39F236589815


Sleep/Wake UUID: F309F613-391B-47C7-9169-A034F89BE155


Time Awake Since Boot: 160000 seconds

Time Since Wake: 7888 seconds


System Integrity Protection: enabled


Crashed Thread: 8


Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000004

Exception Codes: 0x0000000000000001, 0x0000000000000004


Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11

Terminating Process: exc handler [62802]


Final Cut Pro version 11, I'm using it on a Macbook M4 Pro, Sequoia 15.5. 48 G Memory, 500 GB Storage.


Each time I try to select "Transcribe Captions" it crashes, closes the program, and gives me the above message. I have my Final Cut Pro folders on an external hard drive (that is 2TB). I have recently deleted all the library rendering files but it still crashes. Can anyone explain why? Thank you.

6 replies

Whenever the application crashes, delete its preferences. To delete preferences, hold down command and option while starting the application and click Delete Custom Settings. The application will start with default settings and open an "Untitled" library. Adjust the settings, reopen the library you were working, and see how it works now.


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


The only questionable software I notice is the Google updater software. Their terrible keystone software is installed but not loaded, but there's a GoogleUpdater.app that is loaded. Previously the keystone software would damage the video toolbox often requiring FCP to be completely reinstalled after removing all the Google cruft scattered across the drive. The instructions to completely remove everything Google is https://chromeisbad.com


Thanks. I reformatted my external hard drive, restarted my Mac and clicked transcribe captions and it still crashed. I have no idea what to do. I tried a brand new external hard drive, switched it to APFS and it's still not working. Here is the error message:


-------------------------------------

Translated Report (Full Report Below)

-------------------------------------


Process: Final Cut Pro [1156]

Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro

Identifier: com.apple.FinalCut

Version: 11.0 (430149)

Build Info: ProEditor-43000139026000000~9 (2E92d)

App Item ID: 424389933

App External ID: 870244110

Code Type: ARM-64 (Native)

Parent Process: launchd [1]

User ID: 501


Date/Time: 2025-07-14 07:26:36.3819 -0700

OS Version: macOS 15.5 (24F74)

Report Version: 12

Anonymous UUID: 7D0459CE-0833-9975-6B89-39F236589815



Time Awake Since Boot: 210 seconds


System Integrity Protection: enabled


Crashed Thread: 22


Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000004

Exception Codes: 0x0000000000000001, 0x0000000000000004


Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11

Terminating Process: exc handler [1156]


VM Region Info: 0x4 is not in any region. Bytes before following region: 4336615420

REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL

UNUSED SPACE AT START

--->

__TEXT 1027b8000-1028b0000 [ 992K] r-x/r-x SM=COW /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro


+1 on terryb's comment about google updater.


The only other strange thing that I noticed, and cannot find a reason why, is that, although the application has crashed, the report failed to pick up on that - though it does refer multiple instances where FCP had "high cpu usage".