My FinalCut Pro is crashing and does not open. error: Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Final Cut Pro [1554]

NOW it seems I found a solution, because I noticed that yellow caps lock indicator anytime on where I was going to write (very annoying) and Apple doesn't give you any option on how to remove...

WELL following the instruction from another thread here to remove by terminal that indicator, ALL SEEMS TO GOING WELL NOW!

from:

yochees

User level:

Level 1

34 points

Oct 11, 2023 6:08 AM in response to richardm04

Found a solution. In Terminal:

sudo mkdir -p /Library/Preferences/FeatureFlags/Domain

sudo /usr/libexec/PlistBuddy -c "Add 'redesigned_text_cursor:Enabled' bool false" /Library/Preferences/FeatureFlags/Domain/UIKit.plist

Then reboot. After reboot - problem solved.

Hold Opt-Cmd a you launch the application to see if it will open. What version of FCP is this?

Please post an EtreCheck report https://etrecheck.com giving the application Full Disk Access in Privacy & Security rity System Settings. Copy the report rt t and use the Add Text button to paste the result into reply box. 

A Segmentation fault means there may be a programming error somewhere in your active project...

What 3rd party plugins/templates are you using? Can you temporarily disable them and try restarting FCP? Or, can you start up Final Cut from a different user account?

Also, do you have enough room on the drive the library is on? (If there's less than 10% available left, then it's more than maxed out.)

Please post an EtreCheck report https://etrecheck.com giving the application Full Disk Access in Privacy & Security rity System Settings. Copy the report and use the Add Text button to paste the result into reply box. 

HI, HAVE HAD THIS MORNING THE SAME ISSUE ops sorry for capitals...

I just realise that some of the audio extensions could be the issue, so I disinstalxled Isotope, it was not the last version and was not using it anymore from years.

well, everything now is woking perfectly on my final cut pro.

disinstallation does not erase all the plug ins in the main library and also in the application support folder, so I did it manually.

I attach down here my last crash with it.

Check what kind of audio components you have installed and probably it could be that issue )I just upgraded to Sonoma so that's why maybe I began to have issues.

abraço

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

Translated Report (Full Report Below)

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

Process:               Final Cut Pro [5721]

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

Identifier:            com.apple.FinalCut

Version:               10.7.1 (410082)

Build Info:            ProEditor-41000082016000000~12 (1D1004)

App Item ID:           424389933

App External ID:       861999800

Code Type:             ARM-64 (Native)

Parent Process:        launchd [1]

User ID:               502

Date/Time:             2024-01-21 11:20:58.6831 -0100

OS Version:            macOS 14.2.1 (23C71)

Report Version:        12

Anonymous UUID:        E7DF53A6-5E12-C8BC-9152-E4A4C36C7B98

Time Awake Since Boot: 1400 seconds

System Integrity Protection: enabled

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

Exception Type:        EXC_CRASH (SIGABRT)

Exception Codes:       0x0000000000000000, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 6 Abort trap: 6

Terminating Process:   Final Cut Pro [5721]

Application Specific Information:

abort() called

NO.... unfortunately it happened again and probably is the Sonoma the problem...

if could not fix, I will come back to Ventura.... :(

I made as written above, option+command to reset fcp, I opened the project, went to the minute place I was working and close the app.

opened again but the playhead was not at the point I left it.

I did it twice, and it goes not in the place I left it.

this is not regular I think, I usually had timelines with projects where I left the playhead to the point to continue then, and always worked.

this is something strange and could not believe my fcp could not work anymore as before with a M2Max...