Persistent Final Cut Pro Application Memory Error

Even after emptying the three Library caches on my computer, clearing all Final Cut Pro preferences, keeping all media files in their original locations (rather than copying them) and starting with a fresh, new library with no other libraries open, I still am getting the dreaded "Your System Has Run Out of Application Memory" message. The message says that Final Cut is using over 50 GB of memory, but my activity monitor shows that Final Cut is using only 2.41 GB.



[Edited by Moderator]

Mac mini, macOS 14.2

Posted on Sep 4, 2025 7:27 AM

Reply
Question marked as Top-ranking reply

Posted on Sep 4, 2025 12:04 PM

The only thing I notice is that Google's keystone autoupdating software/malware was installed at one point, but is not currently loaded now. A new autoupdater is running instead. The keystone software was notorious for breaking FCP and the system video toolbox. It's possible the new autoupdater is also bad. The advice was to remove all Google software following the instructions at https://chromeisbad.com Simply deleting Chrome was not enough. Sometimes a reinstall of FCP from the AppStore was necessary. I do not allow Chrome on any of our production machines.


You could try creating a new admin user to see if the problem is specific to your user space.


Others may find additional items.


[Loaded] com.google.GoogleUpdater.wake.plist (Google LLC - installed 2025-09-02)
    Command: ~/Library/Application Support/Google/GoogleUpdater/Current/GoogleUpdater.app/Contents/MacOS/GoogleUpdater --wake-all --enable-logging --vmodule=*/components/update_client/*=2,*/chrome/enterprise_companion/*=2,*/chrome/updater/*=2

  [Not Loaded] com.google.keystone.agent.plist (Not signed - installed 2023-12-07)
    <Empty>

  [Not Loaded] com.google.keystone.xpcservice.plist (Not signed - installed 2023-12-07)


23 replies
Question marked as Top-ranking reply

Sep 4, 2025 12:04 PM in response to PP_83

The only thing I notice is that Google's keystone autoupdating software/malware was installed at one point, but is not currently loaded now. A new autoupdater is running instead. The keystone software was notorious for breaking FCP and the system video toolbox. It's possible the new autoupdater is also bad. The advice was to remove all Google software following the instructions at https://chromeisbad.com Simply deleting Chrome was not enough. Sometimes a reinstall of FCP from the AppStore was necessary. I do not allow Chrome on any of our production machines.


You could try creating a new admin user to see if the problem is specific to your user space.


Others may find additional items.


[Loaded] com.google.GoogleUpdater.wake.plist (Google LLC - installed 2025-09-02)
    Command: ~/Library/Application Support/Google/GoogleUpdater/Current/GoogleUpdater.app/Contents/MacOS/GoogleUpdater --wake-all --enable-logging --vmodule=*/components/update_client/*=2,*/chrome/enterprise_companion/*=2,*/chrome/updater/*=2

  [Not Loaded] com.google.keystone.agent.plist (Not signed - installed 2023-12-07)
    <Empty>

  [Not Loaded] com.google.keystone.xpcservice.plist (Not signed - installed 2023-12-07)


Sep 5, 2025 10:14 AM in response to PP_83

What plugins do you have installed? Note that they don't have to be actively in use in the project to potentially cause an issue.


When you got the new Mac, did you migrate everything from the previous one? It's recommended to only migrate the User data, no Applications or System files, then download fresh copies from the AppStore or 3rd party.


As another test, you could install a fresh macOS on an external drive, then boot from that drive, then install only FCP. Don't install any Google apps. Create a new library on that drive and see if the problem still happens.

Sep 7, 2025 10:04 AM in response to PP_83

If you've had this problem on three consecutive different Mac computers, that implies something in common was carried forward each time. The application memory error implies a memory leak within FCP. Historically, a common cause of that was third-party FCP video or audio plugins. FCP on Apple Silicon mandates a new plugin architecture called FxPlug 4.x, which runs plugins out-of-process in an external address space. Prior to that, they ran within the FCP address space, so the slightest error in any plugin could crash FCP.


This yielded improved resiliency to third-party plugins crashing FCP. However it does not totally eliminate it, since an external plugin can hang or become erratic and FCP may be trying to communicate with it.


In some cases, the problem could manifest as FCP instability, not shutting down upon command, or a memory leak.


Take an inventory of what third-party FCP video and audio plugins you are using. Remove and totally de-install any old ones you no longer use. Update any new ones to the latest plugin version.


Sep 4, 2025 7:46 AM in response to PP_83

You have already done some good troubleshooting.

We need to know more.


It is possible that the problem may be due to some third party software interference (antivirus, "cleaners" and "optimizers" often cause severe problems).

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


Also: you may want to test in a new admin account and see if the problem also occurs there or not.

This will further help determine whether the issue is specific to your normal account, or systemwide.




Sep 8, 2025 8:50 AM in response to joema

Thanks, Joema, that sounds like a good possibility. I do have quite a few plug ins from FX Factory and others. And a limited test today of Final Cut on an external drive without any plug ins installed worked well: I didn't get the dreaded "Your System Has Run Out of Application Memory" message.


I'll install only my most critical plug ins to the external drive version of Final Cut and see how things go.


But if the plug ins are the problem, wouldn't that show up on the system report, or the Etrecheck report? It seems like there would be some trace of what triggered the problem. Or maybe not...


Thank you!

Sep 5, 2025 10:45 AM in response to PP_83

Chrome and its background processes are known to cause issues.

FWIW, you can use Chrome without the Google updater running all the time in the background; and, really Chrome is syphoning your data for a living, so why not use a different, safer browser? Even some that use the same underlying engine, like Brave, Opera, or Edge, are far less invasive.


That aside, you also have some other stuff that is at best unnecessary - vpn stuff does not produce the kind of security that most people seem to think it does, and unless used as indicated to tunnel into an office, or school, network, it hinders security rather than enhance it.


Also: you do not need any driver manufacturer software, your mac is perfectly capable of handling your drives without it, so I'd uninstall the WD software unless there is a reason to use it.

Sep 8, 2025 9:55 AM in response to PP_83

PP_83: Unfortunately, a problematic plugin won't usually show up as an error or warning on the system report or Etrecheck. The type of error causing a memory leak cannot be detected by just reading the version info. It is a behavioral condition that only manifests at runtime.


There are methods to debug memory leaks on a production application, but they are complex and usually require iteratively sending files back and forth. For that reason, it's better to first try basic things like you are now doing.


The dilemma is you need to know more than it's leaking -- you need to know what is causing it. That can be done but it requires a highly-experienced person familiar with remote troubleshooting, and a customer willing to try things over many hours or days repetitively.


The goal is to avoid such cases by testing the product itself. Apple strenuously does that, but small plugin developers often don't have the time or expertise. Yet when installing an FCP plugin, it effectively becomes part of the shipping product.


Over the past few years, Apple has taken steps to "firewall" or "sandbox" plugins to contain possible misbehavior. It has improved things a lot but it's still not problem-free.


Sep 5, 2025 1:54 PM in response to terryb

Hi, terryb:


Okay, I installed a fresh MacOS (Sonoma, because I'm not sure about Sequoia compatibility for some of my apps) and a fresh Final Cut Pro on my external drive. In a limited test, it didn't give me the dreaded app memory warning. But I did notice that when I closed out of Final Cut, it spun for a long time closing "background tasks" even though I have background rendering off. And once that was finished, Final Cut didn't close. I had close out again, it took a while to close. So I'm concerned that there's still an issue. But I will try to finish my two-minute project with it and see how far I get, and report back.


Thanks for all of your help!

Sep 5, 2025 8:50 AM in response to Luis Sequeira1

I just tested this with a new Admin account and got the same results regarding excessive application memory usage. Of note: this issue has plagued me through THREE computers, even though I edit short, simple videos (under two minutes long). Each time, I bought a new computer with more memory, hoping to solve the problem, but after a short grace period, it recurs. I got my Apple Mini M2 last year and it seemed to solve the problem for a few months, but now it's recurring.


Also of note: The videos are simple, with few effects, but today when I got the excessive app memory usage note, I managed to open "Background Tasks" and saw "Rendering" active, with 0% complete. So that activity might be the issue, even though it doesn't show on the Activity Monitor.


A YouTube video on this problem which advised deleting library.cache and other files, and also keeping all media files in their original location (which I do) said that Proxy and Optimized media are not required when using Mac M2 machines or later. So I have left those boxes unchecked. But even so, an under two-minute video with few effects wouldn't seem to tax any modern computer.

Sep 15, 2025 7:10 AM in response to joema

Thanks again to everyone for your help! I finished my last (very short) project on the external drive with a fresh installation of Final Cut running without my plug-ins. I'll try that again for my project this week, though I will miss the plug ins. And we'll see if the dreaded running out of app memory returns.


If not, I'll try uploading the plug-ins that I use the most and hope that doesn't break anything. Logging in as a different Admin and rebooting the computer off the external drive when I'm editing is a bit of a drag, especially if I discover that I need a file that's not available without re-rebooting with my original Admin credentials, but I can deal with it if I simply can't fix the problem any other way.


Thanks!

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.

Persistent Final Cut Pro Application Memory Error

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