Skip to main content
Participating Frequently
March 8, 2024

RAM Filling (and sometimes continuing to grow) after Encoding is complete. Freezes AME

  • March 8, 2024
  • 7 replies
  • 267 views

I do all my editing on my primary system, then save the project file to a folder on Dropbox. A remote computer running Media Encoder has that folder setup as a Watch folder to automatically pickup and export the sequences in a project. A number of computers will save projects to that folder and it is supposed to just truck through them, as headless a possible.
At some point we'll notice that projects have stopped rendering and when checking the machine Adobe Media encoder has frozen, and there's a system warning to force quit apps because the computer is out of memory. It's been a relatively consistent issue, but moreso lately.
After force quitting Media Encoder and re-opening it, it picks up with any files that hadn't finished, and goes on it merry little way until it runs out of memory again. The files that it got stuck on proceed through without issue, so it's not centered on the projects or footage themselves, it seems that Media encoder isn't releasing the the memory it uses when projects complete.

Remote Machine Running AME: 
Mac Mini - M1, 2020
MacOS Sonoma 14.2.1
8GB RAM
35GB Available HD

7 replies

Adobe Employee
April 10, 2024

We are aware of memory issues and are working on fixing this. In the meantime the best thing you can do is to restart AME. Sorry for any inconveniences.

Participating Frequently
April 10, 2024

Here are a few screenshots.

 

1) Queue is idle after completing a number of exports a few hours ago, and AME is still consuming 10.69 GB of Memory.



2) After clearing completed exports from the queue, it drops to 5.97GB.


3) After quitting AME, and re-opening it, it's back to a relatively low 450MB.

Participating Frequently
April 9, 2024

After successfully processing jobs, the memory remains high, like some or all of it isn't getting purged/released once a job completes.

Yesterday after six exports completed (with no issues) and no pending/waiting exports, AME was still using 15.98GB of memory.

Clearing the six completed exports from the queue dropped it at 14.6GB. After I quit and restarted AME, it returned to using 2GB.

EckiAME
Community Manager
Community Manager
April 9, 2024

Are you saying that the AME internal memory gets increased when launched and staying idle or did you process jobs and after that the consumed memory remained high?

Participating Frequently
April 8, 2024

Yeah, I'm working on getting it upgraded… However, the issue is more that AME isn't always releasing the RAM after exports complete. Last night for instance, after a full day of exports where it ran fine and everything exported sucessfully, I looked and with no processing or pending jobs, it was using 15.58GB of memory while idle. 

EckiAME
Community Manager
Community Manager
April 8, 2024

Depending on your source footage, 8 GB of RAM might not be enough. This is the absolute minimum. We recommend 16 GB or more. If the application runs out of RAM, it starts swapping on your hard disk which is very slow.

Participating Frequently
March 8, 2024

Also, footage is stored on and exported to Dropbox folders on an External 4TB NVME connected to the Mac Mini.