final cut pro quit unexpectedly

Question

zsoltbarabas Author

Level 1

8 points

final cut pro quit unexpectedly

I've been using FCPX and the Red Giant Looks app for a long time.

Ever since I got my M1 Mac, the problems started.

Now Looks works natively, but FCPX always quits.

It is enough to scroll the timeline left and right and quit. Or the browser scrolls up and down.

It's starting to drive me crazy.

Anybody understand the "problem details"?

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

Translated Report (Full Report Below)

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

Process: Final Cut Pro [23945]

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

Identifier: com.apple.FinalCut

Version: 10.6.3 (405303)

Build Info: ProEditor-40530003015000000~2 (18F3)

Code Type: ARM-64 (Native)

Parent Process: launchd [1]

User ID: 501

Date/Time: 2022-08-01 15:27:42.1788 +0200

OS Version: macOS 12.4 (21F79)

Report Version: 12

Anonymous UUID: BEB18F2B-C456-001C-9258-202D1C3C08C4

Sleep/Wake UUID: 62F762FB-F19A-43CF-83E3-5972BC7DDE6F

Time Awake Since Boot: 310000 seconds

System Integrity Protection: enabled

Crashed Thread: 40 Dispatch queue: com.apple.NSXPCConnection.user.endpoint

Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:

abort() called

Application Specific Backtrace 0:

0 CoreFoundation 0x00000001a3c99198 __exceptionPreprocess + 240

1 libobjc.A.dylib 0x00000001a39e3e04 objc_exception_throw + 60

2 CoreFoundation 0x00000001a3d2cf40 -[NSObject(NSObject) __retain_OA] + 0

3 CoreFoundation 0x00000001a3bf8544 ___forwarding___ + 1764

4 CoreFoundation 0x00000001a3bf7da0 _CF_forwarding_prep_0 + 96

5 Ozone 0x0000000116d1b58c _ZN20OZFxXPCConnectionMap36newXPCConnectionWithServicePrincipalEPvP8NSStringPm + 372

6 Ozone 0x0000000116d1b1c8 _ZN20OZFxXPCConnectionMap21reestablishConnectionEP15NSXPCConnectionP8NSStringPvm + 484

7 Ozone 0x0000000116f62830 _ZN18OZFxPlugSharedBase19updateXPCConnectionEP15NSXPCConnection + 192

8 Ozone 0x0000000116f6274c ___Z21setupPluginConnectionP18OZFxPlugSharedBaseP9PROPlugInP21FxPrincipalAPIHandlerP18OZFxPlugAPIManageriPmPPvS7__block_invoke + 44

9 Foundation 0x00000001a4ab8c30 message_handler + 364

10 libxpc.dylib 0x00000001a38811c0 _xpc_connection_call_event_handler + 152

11 libxpc.dylib 0x00000001a387fb18 _xpc_connection_mach_event + 1136

12 libdispatch.dylib 0x00000001a3988274 _dispatch_client_callout4 + 20

13 libdispatch.dylib 0x00000001a39a7dcc _dispatch_mach_cancel_invoke + 128

14 libdispatch.dylib 0x00000001a39a5430 _dispatch_mach_invoke + 924

15 libdispatch.dylib 0x00000001a398f784 _dispatch_lane_serial_drain + 376

16 libdispatch.dylib 0x00000001a3990438 _dispatch_lane_invoke + 444

17 libdispatch.dylib 0x00000001a399ac98 _dispatch_workloop_worker_thread + 648

18 libsystem_pthread.dylib 0x00000001a3b48360 _pthread_wqthread + 288

19 libsystem_pthread.dylib 0x00000001a3b47080 start_wqthread + 8

Kernel Triage:

VM - Compressor failed a blocking pager_get

"Model: MacBookPro17,1, BootROM 7459.121.3, proc 8:4:4 processors, 16 GB, SMC

Graphics: Apple M1, Apple M1, Built-In

Display: Color LCD, 2560 x 1600 Retina, Main, MirrorOff, Online

Display: ASUS VP28U, 5120 x 2880 (5K/UHD+ - Ultra High Definition Plus), MirrorOff, Online

Memory Module: LPDDR4

AirPort: Wi-Fi, wl0: Mar 23 2022 19:57:59 version 18.60.27.0.7.8.129 FWID 01-570be953

Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports

Network Service: Wi-Fi, AirPort, en0

USB Device: USB31Bus

USB Device: USB3.0 Hub

USB Device: USB3.1 Hub

USB Device: Hard Drive

USB Device: HD710 PRO

USB Device: USB 10/100/1000 LAN

USB Device: Crucial X8 SSD

USB Device: One Touch HDD

USB Device: USB2.0 Hub

USB Device: Echo 11 Thunderbolt 4 Dock

USB Device: USB Audio

Thunderbolt Bus: MacBook Pro, Apple Inc.

Thunderbolt Device: Echo 11 Thunderbolt 4 Dock, Sonnet Technologies, Inc., 1, 30.0

MacBook Pro 13″, macOS 12.4

Posted on Aug 1, 2022 6:39 AM

Reply

Answer 1

Aug 1, 2022 7:07 AM in response to zsoltbarabas

The application crashing to be due to this plugin, or not. There is no way to tell.

Are you sure this and other plugins are up to date?

Also: did you migrate everything from your previous mac to the new one?

Old stuff, or other things can cause problems.

In order for us to have a shot at finding it, please run Etrecheck and post its full report here. Use the "additional text" button and paste the report into the text box.

Reply

Answer 2

terryb

Level 4

3,520 points

Aug 1, 2022 2:00 PM in response to zsoltbarabas

One of your drives is full

Mount point: /Volumes:T*********|
Used 1.92 TB
Size: 2.00 TB
Free: 75.50 GB

You have Chrome and its badly misbehaved launch agents installed. For more info and how to completely remove Chrome (just removing the Chrome.app is not enough), follow the instructions at https://chromeisbad.com Once everything has been removed, download and reinstall FCP.

[Loaded] com.google.keystone.agent.plist (Google LLC - installed 2022-04-18)
[Loaded] com.google.keystone.xpcservice.plist (Google LLC - installed 2022-04-18)

Reply

Answer 3

Tom Wolsky

Level 10

152,816 points

Aug 2, 2022 5:36 AM in response to zsoltbarabas

The crash logs don't really help.

Reinstall FCP from the App Store and if you could post an updated ErterCheck report with Full Disk Access.

Reply

Answer 4

terryb

Level 4

3,520 points

Aug 2, 2022 11:54 AM in response to zsoltbarabas

As Tom requests, a new Etrecheck will be helpful.

A full TimeMachine drive shouldn't be a problem for FCP.

You can do a clean macOS install with a fresh FCP install onto an external SSD and test if the problem is fixed.

Reply

Answer 5

zsoltbarabas Author

Level 1

8 points

Aug 2, 2022 5:34 AM in response to terryb

Unfortunately nothing changes. 3 hours after I removed the chrome correctly and ejected the full "time Machine external drive, crashes again. A lot.

Report added.

I'll try to make a clean osx install and a naked FCPX install. Try to cut few days and if no crash, I'll install step by step the plug ins.

But not now. In the middle of the season no time to do this. Maybe in november.... :) Ahh...

Full FCPX report

Reply

Answer 6

zsoltbarabas Author

Level 1

8 points

Aug 2, 2022 1:54 AM in response to terryb

Thanks!

Yes, this is the Time Machine drive. But before this drive was almost half used (1Tb free) the problem was the same. I'll try to disconnect and work a day without this. Let's see.

I'll also remove Chrome.

Reply

Answer 7

zsoltbarabas Author

Level 1

8 points

Aug 1, 2022 1:48 PM in response to Luis Sequeira1

Report

Thanks your answer. Here is the report.

Reply

Answer 8

zsoltbarabas Author

Level 1

8 points

Aug 1, 2022 1:53 PM in response to Luis Sequeira1

And yes. Everything is the same in this M1 Mac, like my old Intel one. I changed about a year ago and the old system was much more stable and reliable.

Reply

final cut pro quit unexpectedly

Similar questions