Skip to main content
Inspiring
August 17, 2025

P: Premiere Pro v.25.4 'eats' memory

  • August 17, 2025
  • 59 replies
  • 8879 views

  Hi Adobe,
I haven't contacted you in a long time....first let me praise you, you can see that you are working hard and every iteration of Pp is better and better....until this v25.4...the problem is that the new version 25.4 'eats' memory....
T he system is Win 11 pro, freshly installed with all updates (24H2 - Os build 26100.4946),
graphics driver (580.97-desktop-win10-win11-64bit-international-nsd-dch-whql)...
deleted (Media Cache Database, Media Cache Files, deleted rendered files from Adobe Premiere Pro Video Previews) from previous renders
  Kreativ cloud installed.....mostly, when I render a video on the timeline the memory goes up and up until it reaches 64GB, as much as I have and everything stops, even the OS...must restart the system(hard,everything is frozen)...so I was forced to restore v.25.3 and the same I rendered the project,delet (Media Cache Database, Media Cache Files, deleted rendered files from Adobe Premiere Pro Video Previews) and...
memory does not exceed 32GB or 48% of memory usage....

 

my configuration;

RTX 3090TI 24GB
Ryzen 9 3950X
64GB memory
1NVMe M.2 for Os
1NVMe M.2 for video
1NVMe M.2 for cache....ect

 

thank you very much and all the best

59 replies

R Neil Haugen
Legend
September 4, 2025

It's only major version changes that won't open in a previous major version ... we are in the 25.x series now, last year was the 24.x, right?

 

You can't open a 25.x project in a 24.x Premiere, but you can always open a 25.x project in any 25.x version.

Everyone's mileage always varies ...
cendrick1
Known Participant
September 4, 2025

So we are told to revert to a previous 25.? version to have a good working version of pp. Projects saved in say 25.4 will they open in 25.3? I thought they would not open once you upgraded and then saved that project in that newer version.

Inspiring
September 4, 2025

I work on batches of videos usually 4 to 6 videos upwards of 3-6 minutes for each one. After working on the edits I send them to Media Encoder to export. My memory pressure in the activity monitor I've noticed has been running a little higher. Used to hover around 8 Gb now its at 10 Gb out of 24 Gb with not running anything. Running premiere pro and media encoder its now running at 20.83 Gb and when I export videos it goes up to 22Gb out of 24 Gb. Before I would be lucky to hit 19 Gb. This was all before the most recent update from adobe. The issue... when at 22 Gb for a minute adobe encoder stops responding. I try to force quit and the window disappears before I can click it. I have to do this multiple times before I actually can. This has happened for a bit. Noooooow it just completely freezes my computer and I have to a forced reset of my computer. MY WORK FLOW HAS NOT CHANGED for the last 8 months. This has just started happening in the last 3 days. Nothing on my end has changed. I already contacted apple support and we tested this in the safe mode other user and it happened there. We cleaned caches and files and etc. and they say it has to be an adobe problem. I tried to uninstall reinstall. I tried the adobe cleaner tool. Not entirely sure if I did that correctly but I did it anyway and it seems to have made the problem worse. I swear if this is an issue involving Ai Imma crash out. I need to keep the memory pressure down. Theres literally no reason for premiere pro and media encoder to take up all of the physical memory (Apple ram?) and cause it to crash. Litterally none. 

Inspiring
September 4, 2025

Oh yeah forgot to add. Mac Mini M4, Memory 24 Gb, MacOS sequoia 15.6.1

Everything is up to date. There are no updates to do for any applications. 

saarangp
Participant
September 2, 2025

Yup, same issue with 25.4 version and even 25.4.1

But as per the pinned comment by @IanB_360 the devs are working on the issue and workaround is to roll back to 25.3
I was also worried when I encountered this issue last week when a video export was failing at 48% Rolled back to 25.3 and it was successful.

Hope the devs are able to fix this bug soon.

mandicreally
Inspiring
September 1, 2025

JUST Updated to 25.4.1 (Build 3) and didn't fix the issue. The video edit I NEED completed today is now unable to be opened in main Premiere. Beta keeps failing to update too. Idk what is going on but things have been headed downhill for me lately and it is rather concerning to my work.

I have to try and roll back an edit to 25.3 I guess (where Premiere will yell at me and say I can't do that).

Participant
August 31, 2025

It all happened after installing 25.4 version .it was everything good. I rolled back to 25.3 No ram spike. Even 4k rrendering  69%.

R Neil Haugen
Legend
August 31, 2025

Mogrts can have interesting effects on hardware, and there have been from time to time specific bug behaviors with mogrts. That are triggered by certain options in building them at times.

 

So the mogrts themselves ... did you make them? Are they from Adobe stock? Or did you get them somewhere? That would be helpful.

 

Next ... the CPU is mid-level as is your RAM for NLE operations. For comparison, my five year old desktop is 24 cores and 128GB of RAM. And a 2080Ti, while awaiting Nvidia to sort out the crud endemic to their new 50 series cards. It still flies through most things, but I wouldn't say it's a high-end rig as I know many much more powerful machines.

 

And ... the 5060 might be at least part of the problem. As the 50 series card release has been a mess all over the pro video post applications. Not just Adobe apps ... it's on everyone's gear.

 

Some users changed a BIOS setting, and got it going. Some had cards that were overclocked from the maker, and dis-overclocking them got the cards working. Some got their card working simply by trying out different drivers.

 

And many simply RMA'd their card back, and got a card working.

Everyone's mileage always varies ...
Participant
August 31, 2025

When i put some MOGRT file on premiere pro timeline and render effect in and out my ram usage goes up to 99% and pc get freezed and laggy .Even if i remove the MOGRT file from the time line memory stay as its. I have high end pc set up..

💥My CPU is - NTEL CORE I5 14400 (20M CACHE, UP TO 4.70 GHZ)

💥My Gpu is - GeForce RTX™ 5060 8G SHADOW 2X OC.

💥My motherbord is -ASUS TUF GAMING B660M-PLUS WIFI DDR5 MOTHERBOARD.

💥My Ram is - 32Gb

Any Solution ?

mandicreally
Inspiring
August 30, 2025

Just chiming in that I have almost the exact same system specs as the OP and am experiencing the same issue. The problem persists with 25.4.1. Also as the person above me noted, exports take FOREVER compared to 25.3. I was able to export a 30 minute video in basically real time or faster before, now It is an hour plus. Even just trying to export only the audio (something I do for transcribing audio) takes a shockingly long time. Used to take seconds, now it takes a dozen minutes or more.

Massive memory hole when I open a project. Tried to open a video edit I did last month so I could review a section of it and my entire system locked up as my 64GB of RAM jsut maxed out. A video edit that I completed without issue a month ago is now completely unable to be opened today. 


Last week I edited a video that I midway through ran into the same issue. I had to move to the Beta Premeire to complete it. This is why I keep the Beta version continually installed, so I can bounce between the two when some feature gets broken. It is just really sad that I feel a need to do that...

My system:

AMD Ryzen 9 5950X
Nvidia RTX3090Ti
64GB of RAM
Project source files on an all SSD NAS connected over a 10gbe network connection
Cache on a local NVME SSD

I tried clearing the cache and fully resetting Premiere settings on boot. Tried updating to the latest Nvidia studio drivers. Problem persists.

Participating Frequently
August 29, 2025

Hi, Lan. Thank you for the quick fix with the RAM issue in version 25.4.1. The memory management now works as it should. But now the project rendering takes an unreal amount of time. What 25.3 processes in 15 minutes takes more than 65 minutes in 25.4.1 (I didn’t wait for the calculation to finish and stopped the render). I don’t know what the problem is. Maybe something with the CPU/GPU and how Premiere works with them.