P: Premiere Pro v.25.4 'eats' memory

[STUDIO29K]

  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

[Gabriel_Ampiaw4776]

I have downgraded my premier pro to 25.0. Exports and rendering are working perfectly now.

[Shinain]

Hello, I would like to mention that I discovered that MOGRT clips with animated titles were causing memory usage to skyrocket. Without them, the export was successful. I reverted to earlier versions of the software and everything worked correctly.

[defaultttid421kp29i]

@IanB_360 when you say that the current work around is to rollback to 25.4, that only works if Adobe doesn't also remove the ability to rollback to older versions.

"According to Adobe’s official Target release notes, the UI version toggle—allowing users to switch to older versions—was permanently disabled in phases between July 15 and July 30, 2025, with affected organizations no longer able to revert to previous versions except in rare, case-by-case exceptions".

[R Neil Haugen]

I think you misunderstand the roll-back options. It is always based on major version, not patch updates.

You can go back to 24.x if you want to. And certainly all 25.x builds.

[cjones@loft.org]

This is a serious issue! I have even purchased a new computer because I thought it was old hardware not being able to keep up. The new computer shpuld be able to render a 20 minute video with some effects in its sleep. 

Intel Ultra 7, 64gb RAM, Nvidia 5090 GPU. 

All the ram gets eaten up, the screen blanks out, and the system crashes. 

I have latest drivers, cleared cache, and tried videos I'd already cleanly rendered like a month ago. Crashes every time!!!

[R Neil Haugen]

There is an especially serious issue with many 50 series cards also. You might be running into both a RAM issue on top of the 50 series GPU problems. Two things making the whole situation worse.

All the pro video apps have been hit with the 50 series GPU struggles. Some changed drivers,some RMA'd their card. 

Hoping both issues get fixed soon.

[mehdi_8381]

Hello Everyone !

For the past two weeks, I've been experiencing significant slowdowns (and even crashes) when rendering in Adobe Premiere Pro.

At first, I thought it was due to excessive heat since it's summer, and I figured my PC was struggling and that it would pass, but now the temperatures have dropped and nothing has changed...

During rendering, I went to the Windows Task Manager and saw that memory usage is still very high (95%). I don't know if this is normal, but I find it excessive considering that I have a fairly new PC with:

- 32 GB of RAM
- Intel Core i7-14700KF
- NVIDIA GeForce RTX 4060 Ti

I checked the “GPU-accelerated rendering” box to help the processor by using the graphics card. Of course, during rendering, I don't do ANYTHING in the background, I just let the computer run, and yet this happens to me when rendering TIKTOK videos, which are 120 seconds long at most.

It can sometimes take me up to 20 minutes for a 60-second video with a few video clips and images, whereas before it took 120 seconds to render. As you can see above, I have the “RAM available for Adobe Premiere Pro” option at 26 GB. Is that too much? Is that what's consuming too much and causing the rendering to crash?

PS : Of course, I have the latest updated version of Premiere Pro and my drivers are also all up to date. And sorry guys for my english, it's not my native langage.

[Law Jones Pro]

I’m experiencing major stability issues with Premiere Pro after updating to version 25.4. My operating system is macOS 15.6. The app was running normally prior to the update, but since then I’ve encountered the following problems on two different machines:

• New Mac Mini (16 GB memory): Crashes during export with the error: “Your system has run out of application memory.”
• MacBook Pro (32 GB memory): Application fails to launch with the error: “Premiere Pro is damaged and can’t be opened. Move to Trash.” This app was downloaded from Adobe Cloud. 

Both systems are fully updated and show the same issues since upgrading Premiere.

Troubleshooting steps I’ve already attempted (without success):

• Reset Premiere Pro preferences
• Uninstalled and reinstalled Premiere Pro
• Restarted machines
• Closed all other applications while running Premiere
• Cleared Media Cache

Despite these efforts, the crashes and errors persist. This seems like a bug introduced with the 25.4 update.

Could Adobe please advise on next steps, or confirm if this is a known issue with version 25.4 on macOS 15.6?

[IanB_360]

Hi @Law Jones Pro 
There is currently a known issue with memory leaks. Please check if this matches what you see for the Out of Memory error. premiere-pro-v-25-4-eats-memory 

The Damaged APP error is a separate issue. This link provides information on the error for the Damaged app https://helpx.adobe.com/x-productkb/multi/macos-sonoma-permission-issue.html

Here to help

Ian

[LeHerissonCrea]

Hi!

As many of us, i had exactly the same issue: 99% RAM usage, finishing with a total black screen and needed a hard reboot. Even more, my CPU and GPU were barely unused (certainly because RAM was "capping" my other components.

I downgraded to 25.3 premiere AND Media Encoder version and magically, everything works perfectly (my CPU and GPU are now used properly). So there's definitely an issue with RAM in this version.

[Jeremy_TBR]

I've been having a problem after the latest update while exporting where the project will render to a certain point and then just stop at 29%. When I try to cancel, the application stops responding. I'm on a 2025 Apple M4 Max Mac Studio editing 1080p HD video footage from my Sony A7IV.

I've tried exporting the same project on my home Mac and Macbook and run into the same problem. I've also tried exporting using Adobe Media Encoder and still have the same issue. Is there anything I can do to fix this?

[R Neil Haugen]

Often there's a processing error, sometimes a processing order one, at the point where it stops. And as it is stopping the same place every time, you need to find the spot it stops at.

Select say the first quarter of the sequence, and export only that. Then the next quarter, and on. Find the spot, rebuild it.

[Smushkan]

Throwing another datapoint into the ring...

• Windows 11 24H2
• Intel i5 13600k
• GTX 1070
• 64GB RAM
• Attempted exporting to both a local nVME SSD and to an external NAS, both with terabytes of free space

Sequence is just over 1 minute at 2160p50, all media is Sony XAVC-L.

This issue appears to only be affecting sequences containing a significant number of After Effects MOGRTs for me. In my case the sequence is 100% covered in MOGRTs from start to finish.

I've exported other sequences with far longer durations without issue that only contained a few or no MOGRTs without issue.

The export proceeds normally until it hit about 60%, with RAM gradually climbing to 100% through the process. The export then appeared to get stuck at ~60%, after which RAM occasionally dropped to 95% before rising again and progressing a few more percent. It would then present an error message which was different every time. Occasionally my entire display would black out. The last error message I got was:

Component: Apple ProRes MXF OP1a of type Exporter
Selector: 17
Error code: -1609629695

(Sorry I did not capture the full text.)

Closing the export failure message did not free up the RAM, so subsequent attempts at exporting fail even sooner.

Downgrading to 25.3 allowed me to export the sequence.

[AskMP]

Has anyone tested what seems to be the new release? 25.4.1? I'm not seeing any changelogs listed on Adobe's site for it but I'm updating now to see if it resolves the issue. I will report back if it seems to resolve the problem. Otherwise, consider my 64GM of memory in the list of people having a similar problem. My work around for the last week has been to split assets up into chunks and merge them. VERY unproductive but deadlines need to be met.

[AskMP]

35.4.1 is a bust too... also gave me a VERY strange licensing bug where it thought my one system had over 10 licenses out oft he 2 assigned to it.

[STUDIO29K]

No, the problem is not solved even in v 25.4.1 ('eating memory') - I tested it right after release...for now the most stable version is 25.3..Adobe is working on that problem...thank's...

[rusregio]

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.

[mandicreally]

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.

[The_Mindfulness1114]

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 ?

[R Neil Haugen]

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.

[The_Mindfulness1114]

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%.

[mandicreally]

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).

[saarangp]

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.