I've done everythign suggested on this forum and Final Cut still crashes every few minutes.

Final Cut Pro is doing three things regularly:


- Beachball of death for around a minute and then unfreezing. (Least common)

- Beachball forever (or until I restart FCP) (most common)

- “Your system has run out of Application Memory” Error Screen with Final Cut Pro popping up using anywhere from 50 to 76 GB of memory. At the same time I’ve noticed that when FCP is rendering, the available space on my local disk that appears in my finder windows will drop by 20-50 GB. But as soon as FCP is forced closed, it returns to normal. This happens despite the fact that my FCP library is set to store Cache and Media on my external drive (which it is doing).


This happens no matter what kind of activity I’m doing on FCP: Scrolling through the browser, moving a basic text around, playing back the timeline. Anything can trip it.


An almost complete list of my attempts to rectify this:


- Deleting Chrome and everything chrome related in the both system and user library folders.

- Deleting every FCP plugin and every piece of software I don’t need.

- Restarting the computer many times.

- Trashing preferences many times.

- Clearing the NVRAM (or whatever that funky restart is called)

- Trashing and re-installing FCP.

- Starting a new FCP library.

- Starting a new FCP project/timeline.

- Switching External Hard Drives (from a toaster/internal to an external HD)


I’m certain there is more but this is all I can remember right now.


Please help I’m already passed my delivery deadline for this project. Big thank you!

MacBook Air 13″, macOS 12.5

Posted on Mar 27, 2023 9:52 AM

Reply
Question marked as Top-ranking reply

Posted on Mar 27, 2023 10:07 AM

Good job troubleshooting this so far.


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


It is not surprising that available space drops and then is recovered - this indicates that something is causing a memory leak (FCP is using more and more memory), and using virtual memory until it crashes.


This could be due to several things, among them: corrupted media; and software issues, like third party daemons or extensions. Hopefully the Etrecheck report may flag something.



Similar questions

22 replies
Question marked as Top-ranking reply

Mar 27, 2023 10:07 AM in response to piedralibre

Good job troubleshooting this so far.


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


It is not surprising that available space drops and then is recovered - this indicates that something is causing a memory leak (FCP is using more and more memory), and using virtual memory until it crashes.


This could be due to several things, among them: corrupted media; and software issues, like third party daemons or extensions. Hopefully the Etrecheck report may flag something.



Mar 27, 2023 9:15 PM in response to Tom Wolsky

I tried it out on a friend's computer and exact same results. So its not the hardware.


Attempting to export the timeline fails always at 34% (does that suggest there's something corrupted about a third way through the timeline?). I've tried reinserting all the clips around that timecode and still crashes on rendering or exporting.


I've learned that if I turn off background rendering, FCP doesn't crash and seems to run normally.


When the export approaches 34%, in activity monitor something called VTDecoderXPCService goes up to 500+% CPU use, with Kernel_Task taking up an additional 100+%. See attached photo...

Mar 28, 2023 5:17 AM in response to piedralibre

You're looking at the CPU. Look at the memory pressure.



Is your friends system the same as yours? Same OS? Have you updated the the OS? There was a problem where the memory pressure would increase during export. This was generally with certain types of media, XDCAM and some others. The work around, which I thought was fixed in an OS update, was to watch the memory and as it built up to start playing files in the browser. It would force the system to release the decoder from the export process and stabilize the memory.

Mar 27, 2023 11:08 AM in response to piedralibre

The system is full. Minimum 15% free space, 20 is better. 10% is finished. System snapshots will eat it up in no time. Your external drive is kinda slow. You're going to struggle with Neat as it's very processor intensive and needs to call up content from the eternal. Cache is on the external you said. Those can be large files that need a lot of throughput. You might want to think about working with proxies.

Mar 27, 2023 10:49 AM in response to piedralibre

Kernel Extensions:

/Applications/Smart Switch/SmartSwitch.app

[Not Loaded] ssuddrv.kext - com.devguru.driver.SamsungComposite (1.6.0 - SDK 10.9)



Your mac does not need this in order to access your Samsung SSD. Thir party drive manufacturer software is not needed and can cause trouble.



User Launch Agents:

[Loaded] mega.mac.megaupdater.plist (Mega Limited - installed 2023-03-27)

Executable: /Applications/MEGAsync.app/Contents/MacOS/MEGAupdater



[Running] MEGAsync (Mega Limited - installed 2023-03-27)

Application

/Applications/MEGAsync.app



I have no sympathy for megaupdater and similar stuff. They can be a breeding ground for adware.

Mar 27, 2023 11:29 AM in response to piedralibre

piedralibre wrote:

Just trashed smart switch. I though I had already gotten rid of it, my bad. (What do you use to access your Samsung with a Mac?)


Not just with Samsung, but with any other HD or SSD I have ever got, I just plug it in, format it if necessary (many drives may come formatted for windows) and use it. The mac has all the software required to use the drives.



Also. I use Megasync to automatically upload my project files to the cloud. Very useful service for me, you think its the problem? I've used it for years.


Maybe this is ok.

Sorry, I may have confused this with some aggregate sites that redestribute software, often laced with adware.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

I've done everythign suggested on this forum and Final Cut still crashes every few minutes.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.