Final Cut Pro needing to be Force Quit after running out of application memory

Question

Level 1

4 points

Final Cut Pro needing to be Force Quit after running out of application memory

During a large, compressed 4K video export on Final Cut Pro, I'm consistently met with a warning that my computer is "out of application memory", which forces me to quit the application and end my video export. I own an 13 inch, M1 chip MacBook Pro with 16GB of RAM and 155GB remaining on my boot drive. The 4K footage is being referenced from external hard drives and no footage is being loaded from the boot drive. I've investigated this issue and taken the advice of given to those with the same problem. Namely, I've deleted my preferences on FCPX, turned off all other applications during export, deleted Chrome and its corresponding keystone daemons. restarted the computer, and deleted + reinstalled FCPX. I;'m trying to determine why Final Cut Pro is using so much memory for this work. If anyone can assist with this, I'd be immensely grateful. Attached is the relevant Etrecheck report.

Etrecheck Report

MacBook Pro 13″, macOS 14.1

Posted on Dec 6, 2023 3:27 PM

Reply

Answer 1

Top-ranking reply

terryb

Level 4

3,642 points

Dec 6, 2023 6:18 PM in response to Chaotix7

I use Time Machine and am not familiar with Cleverfiles. It looks like it's loaded and always running.

[Running] com.cleverfiles.cfbackd.plist (Justin Johnson - installed 2022-09-19)
    Executable: /Library/Application Support/CleverFiles/BackService.app/Contents/MacOS/cfbackd

I also notice an Adobe utility that is automatically launched:

[Loaded] com.adobe.ccxprocess.plist (Adobe Inc. - installed 2022-12-04)
    Command: /usr/bin/open -a '/Applications/Utilities/Adobe Creative Cloud Experience/CCXProcess/CCXProcess.app'

Did you try removing the 3rd party AU plugins?

Did you try rolling back to 10.6.10?

You could try creating a new Admin user, logging in as that user, deleting FCP preferences for good measure, creating a new FCP library and representative project, and exporting.

Reply

Answer 2

terryb

Level 4

3,642 points

Dec 6, 2023 4:58 PM in response to Chaotix7

I'm sorry I don't have any solutions for you but in the report I see iOSScreenCaptureAssistant Crashes, which I believe have been reported here from other Sonoma users. Tom may be more familiar with this and chime in.

There's also CoreAudio reporting crashes. It's possible one or more of your 3rd party AU plugins has problems. You could test by temporarily removing them from your ~/Library/Audio/Plug-Ins/Components directory.

2023-12-05 20:39:11 iOSScreenCaptureAssistant Crash (22 times)
    Executable: /System/Library/Frameworks/CoreMediaIO.framework/Versions/A/Resources/iOSScreenCapture.plugin
    Details:
      libdispatch.dylib: API MISUSE: Resurrection of an object


  2023-12-03 20:59:30 CAReportingService High CPU Use
    Executable: /System/Library/Frameworks/AudioToolbox.framework/XPCServices/CAReportingService.xpc/Contents/MacOS/CAReportingService

Reply

Answer 3

Chaotix7 Author

Level 1

4 points

Dec 6, 2023 5:14 PM in response to terryb

The iOS Screen Capture Crashes are anomalous to me, admittedly. You see, I downloaded Sonoma just yesterday in the hope that updating would thwart a bug that might have caused all this. I'm not sure if Final Cut Pro is supposed to use so much virtual memory during an export (to the point of crashing), but given the other similar incidents of this kind, I'd be willing to bet it's not.

Reply

Final Cut Pro needing to be Force Quit after running out of application memory

Similar questions