Skip to main content
Participant
June 6, 2023

Media Encoder quickly fills up to 100% GPU memory, stops working

  • June 6, 2023
  • 5 replies
  • 343 views

I'm having a real doozy of a problem, and of course it's happening a couple of days before I have to send in a bunch of deliverables...

 

On my current project, whenever I try to output anything, Media Encoder quickly uses up all my dedicated GPU memory, at which point it basically stops rendering. If I'm sending out multiple smaller outputs, each one eats up a chunk of GPU memory, and then the next one eats up another chunk - i.e. the usage increases step by step, instead of going up for one output, then down when that's finished, and up again for the next. The only way I can clear the GPU memory back to zero is to quit Media Encoder (and After Effects), so I pretty much can't queue up more than one output at a time - overnight batch renders are definitely out.

 

Any thoughts? It's driving me a little crazy at this point. Switching to software-only in Media Encoder doesn't seem to help.

 

One possibility: I'm working with ArriRaw footage - any bugs around that? We're in finishing, so it'd defeat the point a little to not link back to the original footage. 

 

I'm using a Windows 10 setup, Ryzen 9 5950X with an RTX 3080, 64GB RAM, most recent AE and ME releases, most recent graphics driver (I tried rolling back to one from last year, no luck). Any suggestions appreciated since I'm going to struggle to strike masters at this point.

5 replies

Participant
February 5, 2025

Just saw some new posts on this thread. I'm still having this problem, many months and many versions of AE / ME / drivers later. I've mostly just given up on batch encoding - I have to quit After Effects and Media Encoder reasonably regularly when I'm striking outputs to clear my GPU memory. Deleting finished renders from the ME queue also helps for some reason - somehow they're still sitting in memory even after they're completed. I've assumed it was something specific about my setup on my computer, intrigued to hear it's happening on Apple too.

Adobe Employee
February 5, 2025

This is possible. Restarting between encodes might be a good thing for now.

Participant
February 2, 2025

I am on a M4 Macbook Pro using Media Encoder 25.1
Perhaps there is a memory leak?
The more files I render the greater the amount of memory being used (using Activity Monitor to see). Gradually, it will take over all of my system memory until no app can run and a system warning dialog appears. Restarting Media Encoder seems to reset the memory usage.

Adobe Employee
June 15, 2023

As per current behavior and testing data available for Arriraw, testing this behavior on both 23.4 and 23.5 seems to be pretty much similar. That is , GPU Memory utilized up to 100% but don't see any crashes in AME with both old and new versions.

Would you be able to sharet the specific media and steps to replicate as well which leads to a crash situation? Our GPU Acceleration guys would like to look into the issue more. I can private message you the instructions in this forum.

Another question: Did you also test in betas?

Community Manager
June 12, 2023

Hi @bpwebster222 ,

Sorry for the problem. Can you please mention your AME/AE versions? 

Moreover, we have done some memory optimisations for ArriRaw footage in the latest beta builds. Please check out the latest beta build version from the creative cloud and let us know how it goes there.

You can download the latest Beta builds from Creative Cloud --> Beta apps --> Premiere Pro (Beta)/Media Encoder(Beta) 
https://helpx.adobe.com/x-productkb/global/creative-cloud-public-beta.html

 

If you still face this issue, please share your project files(&media)/screen-recording here https://helpx.adobe.com/creative-cloud/help/share.html and we will check on our end.


Thanks,
Mayjain