Final Cut Pro (10.6.5) - crash at various stages

There is a known problem in 13.2. The number of items in an event cannot exceed 300 for some systems (some can go higher).

This indicates that problem

informContainerThatSubviewsNeedUpdateConstraints

You can try to reorganize your library inside FCP to reduce the numbers in each event and see if that helps.

FWIW, a few more technical details on the problem: While causally related to an approx 300 clip per event threshold, the underlying issue is apparently related to the AppKit framework "constraint" system. I suspect this changed (maybe inadvertently) in Ventura 13.2, causing FCP to crash.

In GUI programming, constraints control how UI elements are positioned and resized in response to changes in the size and shape of the window or screen. There is a facility called Auto Layout which allows the programmer to define the relationships between UI elements by adding constraints, such as "this element should be centered horizontally in its parent view". Auto Layout then uses these constraints to calculate the position and size of the elements in your user interface at runtime. The goal is to make it easier to create flexible, adaptive user interfaces that look good on different screen sizes.

Related concepts are views and subviews. A view is like a container for other views or graphical elements, such as images, text, and buttons. A subview is a child of the parent view, and the parent view is responsible for positioning and sizing the subviews.

It appears there were calls to update column separator positions (maybe related to populating clips in the Event Browser) then for some reason AppKit disabled a runtime engine related to Auto Layout, maybe for some valid reason. After that it got stuck in a recursive call to -[NSView _informContainerThatSubviewsNeedUpdateConstraints], then crashed.

Observationally it also seems related to the project, however the crash is probably triggered by the underlying UI code that manages the project and Event Viewer UI elements.

I thought all those app frameworks are pulled into the executable at build time, which means nothing in FCP has changed since 10.6.5 was released on 10-24-22. Something at a lower level in the OS that supports those must have changed in Ventura 13.2.

I thoroughly tested FCP 10.6.5 on Ventura 13.2.1 using up to 15,000 clips in a single event and 15,000 clips on a single 42-hour timeline. It got a bit sluggish (not unexpected) but it did not crash. That's quite an improvement from a 300 clip-per-event threshold!!

You have the ghastly "cleanmymac". Completely uninstall this.

You have "ccleaner" - which I gather is a necessity on windows pcs, but certainly not in mac; you don't need or want this running in the background permanently.

You have chrome, and its evil keystone agents.

Completely uninstall - see https://chromeisbad.com for an explanation of the harm they do and how to uninstall them completely. It is not enough to drag chrome to the trash.

After uninstalling, you will need to delete FCP and download a fresh copy from the App Store.

If the Mac computer hangs and turns itself off, that is most likely a system or hardware problem. The fact FCP is running is coincidental. If bridge collapses when a heavy but legally loaded truck drives across, it is not the truck's fault. The bridge has a defect. FCP is imposing a normal, "legal" operational load on the underlying system.

Like other modern operating systems, MacOS enforces strict isolation between the address space of each process. This is ultimately governed by the memory management hardware inside the CPU. No user-mode app whether by accident or intent can crash the operating system. If so all systems would be crashing every day. The exception is an app using a kernel extension which becomes part of the OS full total hardware and memory access. Those can easily crash the OS.

This should be pursued with MacOS or hardware support. There is no source code change in FCP that will avoid a MacOS kernel panic or shutdown.

If your machine shuts down or restarts spontaneously, the MacOS kernel panic info is normally written to a file of the format Kernel_DATE-TIME_user.panic, which is contained in /Library/Logs/DiagnosticReports. It should also be visible in the MacOS Console app, I think under the category "Crash Reports". However sometimes MacOS will not be able to write the file. As a precaution if you see any crash dialog during the crash or after the system reboots, save that to a file or take a photo with your cell phone.

My first guess after examining the Etrecheck output is a kernel extension. You have one for VirtualBox. Any bug in any kernel extension can crash MacOS. That is why Apple has deprecated those for several years and it is incumbent upon those application developers to update their apps to use the new system extension method, not a kernel extension. System extensions run in user mode, not kernel mode and are much safer.

It should do. Depending on you computer it might not be that easy or quick.

A quick test on an M1 Max MBP indicates that the problem is resolved in 13.2.1 that was released today.

You can download MacOS Ventura 10.3.2.1 NOW . Try this.

I've tried it and it's working fine.

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