-
Crash Report Help
Hi. FCPX keeps crashing. Is anyone out there good at reading crash reports that can help me figure out why? TY.
-
3 Replies
-
I’ve read in a number of forums that Ventura 13.3 broke FCP. It often hangs while loading Audio Units plugins. 13.3.1 has been released, but I haven’t heard if it fixes the FCP issue. If you upgraded to 13.3, try going back to 13.2.1.
-
Most of the recent crashes and hangs are related specifically to the discontinued Accusonus ERA audio plugins. This video from Matthew O’Brien explains the process of making sure you find all the pertinent files to remove and fix the situation.
-
It crashed in thread 59. That was in a deep call stack involving “Helium” functions. Helium is a private FCP framework that is apparently related to video processing or rendering. It was processing a queue of items managed by Grand Central Dispatch (GCD). IOW it was likely a worker thread managed by GCD on behalf of the FCP application.
The crash was in ProGL::ContextHandle::getVirtualScreen() const + 0. ProGL is a private FCP framework that might be a wrapper for OpenGL calls. With the advent of Metal I don’t know how that fits in, whether they retained former method names for compatibility with upper layers, or what.
Prior to the crash point it was in the private FCP framework “TextFramework”. That is a Motion framework, which implies Motion functions might have been processing some kind of text or title.
At the top of the crash log, it lists error code “KERN_INVALID_ADDRESS at 0x0000000000000010”. That suggests that the application tried to access an invalid memory address (0x10) that is not mapped or is in a restricted memory area.
It then said “Termination Reason:”, which indicates the process was terminated due to a segmentation fault (Code 11), which is a specific type of memory access violation that occurs when a program tries to access an invalid memory address.
“VM Region Info” indicates that the address 0x10 is not in any region, which may confirms an invalid memory access.
The crash point might indicate a null pointer dereference or an uninitialized pointer in the ProGL library, specifically in the ProGL::ContextHandle::getVirtualScreen() method.
Why that happened in this case is unknown but that’s a typical failure mode when multithreaded software crashes.
Can you give any additional info on what you were doing when it crashed? If it’s reproducible, is there anything in common? Can you export a project XML, create a new library, import the project XML and see if it happens there? If it does, duplicate the project, open the duplicate, select all clips with CMD+A and remove all effects with Edit>Remove Effects. Then see if that project crashes.
I didn’t see any references to 3rd-party plugins in the crash log but if you’re using any, state which ones.
If your computer has multiple monitors, as a troubleshooting step unplug that and any outboard video hubs and see if it crashes without that.
As always try the usual stuff such as reset FCP preferences, verify that all disk volumes have plenty of free space, etc.
Reply to this Discussion! Login or Sign Up