Crash on macOS 13.2 & Final Cut Pro 10.6.5 due to large amount of files #86
Assignees
Labels
Comments
|
Here's an example of the crash log I keep getting. It's also happening on 13.2 for me, most recently when moving/copying events (which, with hindsight, I shouldn't have done since I've now lost my event everywhere except the backup). The event I'm working on has 400 clips; all stored on an external volume. |
|
This crash log is very interesting. It looks like there's some bug in AppKit itself. |
|
As requested Chris, here's my crash log. Looks the same as the above user! |
|
These logs all seem consistent. What Macs are you all using? Mine's a Mac mini M1 with 8GB. (Yes, I should have specced 16GB and I'm kicking myself daily...) |
|
Studio M1 Max, 64GB. |
|
Well, this is certainly interesting! It certainly seems like something is fundamentally broken/changed in AppKit. I have no idea why this would only trigger in macOS Ventura and not Monterey. Hopefully this is an easy one for Apple to solve and they can just push out a FCPX update. Maybe related: Note to self - these are the interesting sections from the above two crash logs: |
|
Just a follow-up to this issue, I've found copying the project into a new event (without copying the associated media) means I can work on the timeline without crashes, so that does confirm to me that it's related to a large number of clips inside an event. |
|
This is now fixed in macOS Ventura 13.2.1. Woohoo! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some users are reporting constant crashes with complex Final Cut Pro libraries. Simple actions like changing the role on a browser clip or adding it to the timeline will crash Final Cut Pro. Dragging and dropping files from Finder will also crash Final Cut Pro. Trashing preferences has no impact. This only started happening after upgrading to macOS 13.2.
It's been reported to Apple, and it's a known issue affecting several apps that are dealing with a large number of files. The root cause is not yet known, and no workaround has been announced.
We currently don't have any data on whether it's on both Intel and Apple Silicon.
The text was updated successfully, but these errors were encountered: