Skip to main content
Inspiring
August 17, 2025

P: Premiere Pro v.25.4 'eats' memory

  • August 17, 2025
  • 59 replies
  • 8885 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
August 20, 2025

That should be enough, don't you think? 😉

Everyone's mileage always varies ...
Participating Frequently
August 20, 2025

R Neil Haugen
Legend
August 20, 2025

Wow, just ... wow. That would be maddening. In the extreme!

 

How much free space do you have on the disc you're exporting to, just in curiosity?

Everyone's mileage always varies ...
Participating Frequently
August 20, 2025

Guys, the problem is that Adobe Premiere or Encoder do not experience any issues with the rendering process itself—as a software operation. In other words, nothing unusual happens inside Premiere or Encoder. That’s why it’s impossible to record any Premiere logs—they simply don’t crash on their own. So, there are no crash logs or dumps in the Adobe log folder. The rendering process just ends up filling the RAM and swap disk, and once the disk is full, the system simply goes into a black screen.

Participant
August 17, 2025

I am experiencing a serious issue with Adobe Premiere Pro after the latest update. The program is consuming almost all of my system memory (up to 95%), which causes the application to freeze or crash during rendering.

This problem did not exist before the most recent update.

Participating Frequently
August 21, 2025

same.

IanB_360
Community Manager
Community Manager
August 19, 2025

@STUDIO29K 
I moved this to your main post from August 18th. We understand frustration when things are not working as they should, but it helps to have a single post for your issue. We will focus on the information you have here and help you out the best we can.

Here to help

Ian

Participating Frequently
August 19, 2025

Memory Management Issue in Premiere and Encoder

Dear Adobe,

The memory management in the current versions of Premiere and the Encoder is not functioning correctly. Memory limits are not being enforced, and memory is not being cleared during the processing of large projects. As a result, memory usage continuously grows, consuming all disk space and causing black screens and system crashes.

This issue needs to be addressed and fixed ASAP.

Best regards,
RR

IanB_360
Community Manager
Community Manager
August 19, 2025

Hi @rusregio 

Welcome to the Premiere Pro Forum community.  Thank you for taking the time to report a problem. The team needs a little more information to begin troubleshooting. The link here, How to Report a Problem, has steps to provide more information about your bug that can help us identify the issue. 

Here to help.

Ian

IanB_360
Community Manager
Community Manager
August 18, 2025

Hi @STUDIO29K 
Are you getting an Adobe crash report before your system freezes up? Have you tried cutting a subclip of one of the Camera files into a new sequence and then trying rendering? What is the Total Running Time of the sequence you are rendering?
The project file will help us better understand what you are facing and speed up the process of elimination. It is understandable if you do not wish to share the project or files; we can try other ways to help resolve the problem. 
Here to help.

Ian

 

STUDIO29KAuthor
Inspiring
August 18, 2025

source files in the sequence:

General
Complete name : H:\SC 2014\ProRes 422 HQ (4;2;2)\MIX1.mov
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt 0000.00 (qt )
File size : 141 GiB
Duration : 1 h 2 min
Overall bit rate mode : Variable
Overall bit rate : 325 Mb/s
Frame rate : 50.000 FPS
Encoded date : 2015-06-26 14:01:26 UTC
Tagged date : 2015-07-06 20:50:35 UTC
Writing library : Apple QuickTime
TSC : 5000
TSZ : 100
Conformance errors : 1
mdat : Yes
0x00000000 : Yes
General compliance : Element size 151846588825 is more than maximal permitted size 151845323572 (offset 0x2C)

Video
ID : 1
Format : ProRes
Format version : Version 0
Format profile : 422 HQ
Codec ID : apch
Duration : 1 h 2 min
Bit rate mode : Variable
Bit rate : 323 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 50.000 FPS
Color space : YUV
Chroma subsampling : 4:2:2
Scan type : Progressive
Bits/(Pixel*Frame) : 3.112
Stream size : 140 GiB (99%)
Title : Core Media Video
Writing library : Apple
Encoded date : 2015-06-26 14:01:26 UTC
Tagged date : 2015-06-26 15:04:59 UTC
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio
ID : 2
Format : PCM
Format settings : Little / Signed
Codec ID : lpcm
Duration : 1 h 2 min
Bit rate mode : Constant
Bit rate : 2 304 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Bit depth : 24 bits
Stream size : 1.00 GiB (1%)
Title : Core Media Audio
Encoded date : 2015-06-26 14:01:26 UTC
Tagged date : 2015-06-26 15:04:59 UTC

Other
ID : 3
Type : Time code
Format : QuickTime TC
Duration : 1 h 2 min
Bit rate mode : Constant
Frame rate : 50.000 FPS
Time code of first frame : 00:00:00:00
Time code of last frame : 01:02:16:23
Time code, stripped : No
Title : Core Media Time Code
Encoded date : 2015-06-26 14:01:26 UTC
Tagged date : 2015-06-26 15:04:59 UTC

 

the files are big, 20GB each...it's a concert...everything was rendered normally on the timeline until version 25.4...when I installed everything new, including the OS and drivers and updates and v25.4 Pp...the same project when rendering in version 25.4 increases the memory to 64GB and then everything freezes and has to be hard reset...it's been a long time since I had any problems with Pp in version 25.3 and below, everything works normally (rendering timelines)...I don't know how to send you such large files, and I don't think there's any point in sending you when everything worked fine until now in v25.3 and below...
  of course, there are a lot of effects, but it all worked normally until version 25.4

 thank's....

IanB_360
Community Manager
Community Manager
August 18, 2025

Hi @STUDIO29K 

What are the source files in the sequence that you are rendering? Could you file share the project and one of the files that are in the sequence you are rendering? 

Here to help

Ian

STUDIO29KAuthor
Inspiring
August 19, 2025

i know it's the holiday season... and please fix this bug in v.25.4...it eats memory...it eats memory!!!

and don't send me answers and questions, simple, 25.4 eats memory when rendering, 25.3 works perfectly....
thank's...

R Neil Haugen
Legend
August 19, 2025

Thisvis annoying, of course. Total sympathies on that. But sadly, this was a nearly useless post.

 

Why? There's like two posts of users with this, and no one else.

 

None of the rest of the user base seems to have this, so logically it is something tied to your system.

 

"We" would need to know your system details to even start sorting this out.

Everyone's mileage always varies ...