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

[????_????6486]

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.

[IanB_360]

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

[STUDIO29K]

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]

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

[STUDIO29K]

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]

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.

[rusregio]

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]

@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

[IanB_360]

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

[rusregio]

Hi, Lan.

Thank you for your assistance.

I am experiencing a critical memory management issue in Premiere Pro version 25.4. 

My System Information:

Issue - The memory usage grows uncontrollably, and after the physical RAM is exhausted, the swap file starts growing. When it completely fills the disk, the system goes to a black screen and becomes unresponsive until I force a restart using the hardware reset button.

File encoding:

The memory limit settings in Premiere and Media Encoder do not affect memory usage — it simply fills all 32 GB of my PC’s RAM and then starts using the swap file. When the system disk is completely filled, the entire system crashes. I manually redefined the swap file size, but this did not help. In the Task Manager, when monitoring system resources, it can be seen that in Premiere version 25.3 the memory limit settings correctly prevent the program from exceeding the limit. In version 25.4 on my machine, this limit is completely ignored. I had to delete all system logs and roll back to version 25.3 (Pr, AE, AME) because I was clearing space on the system disk and needed to finish my work. Unfortunately, I can only provide screenshots of my system at this time.

Here is a screenshot showing how the memory should behave during rendering of this file in Media Encoder. The same applies to Premiere as well.

In version 25.4, during rendering, the parameters in this window were as follows:

In Use (Compressed) 32 GB,

Committed – 76 GB / 146 GB,

Cached 10.8 GB,

Available 0 GB.

And my system drive was completely filled after 5 minutes of rendering. The system would go to a black screen, and I had to restart the computer. After rolling back to version 25.3, I was able to render the file without issues and browse the internet at the same time. 

I made three attempts with system restarts. The logs showed errors first in all peripheral devices, then in the chipset, and finally in the kernel — meaning the memory ran out and the computer sequentially crashed all system processes within one second. If you are unable to identify the problem, I will try to install Premiere and render this file in it, recording the logs and taking screenshots of the Task Manager.

RR

[rusregio]

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.

[R Neil Haugen]

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?

[rusregio]

[R Neil Haugen]

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

[R Neil Haugen]

Oh, and you're exporting into a folder too, and not the drive root?

[rusregio]

same.

[Thomas3014723051e2]

Hi guys,

So recently ive been trying to export an hour long video, and have had the same error but at different time codes come up.

Following the: error compiling movie, Frame creation error, Bad allocation while creating disk aligned video,

another error sometimes pops up, adobe is running very low on system memory.

I think ive tried almost every potential fix i could find:

- Changed virtual memory size

- New sequence method

- Exporting in 5 minute exports

- Exported entire 4k video and then added graphics later to lessen the memory use

- Restart 

- Uninstall

- Software encode & Hardware encode

In case you were wondering i also have high specs 

32 gb ram 

RTX 4070

Intel core i9

Would love some help on this as now it seems to affect all my projects.

More information to note

- i see my ram usage percentage end up hovering around 90-96% in task manager.

- Allocated 24gbs fro adobe to use have even tried higher and lower

[bubmaik]

OMG! I'm having the exact same issue. I thought initially my PC was acting up. Until I started working on my laptop and the same Sh*T kept happening. Paying a lot for a subscription and they give us this damn shitshow. Rolling back to the previous version

[IanB_360]

Hi @Thomas3014723051e2 

The team is aware of the issue, which affects Windows and Mac systems, and is working diligently to resolve it. The current workaround is to revert to another Premiere Pro version, such as 25.3. This will help avoid the memory leak until we have a solution in place. Once we have that solution, we will update the community. 

Here to help

Ian

[MarekMularczyk]

I'm having a similar issue. Although it's not using all the memory but it is using a lot of it

[Gabriel_Ampiaw4776]

Same issue and it's crazy. Have a lot of work to do and behind on deadline 

[MarekMularczyk]

It seems like going back to the previous version would be the solution for now

[STUDIO29K]

https://community.adobe.com/t5/premiere-pro-bugs/serious-issue-with-adobe-premiere-pro-after-the-lat... 

[STUDIO29K]

Mr R Neil Haugen...

what do we look like to you (guinea pigs)....it was not difficult for me to install Pp v25.4 on 4 different systems, with all updates and the latest drivers... and these are...

Win 11 pro 24H2
Win 10 pro 22H2 for Worstation (Windows 10 2023 Update | Version 22H2)
Win 11 24H2 IOT Enterprise LTSC
Win 11 Pro 24H2 win for Worstation

And the v25.4 version behaves the same way...EATS MEMORY...no matter how much you have...

So yeah, it makes your engineers work harder...and finally, when you can pay so much to your programmers who make buggy Pp, you can also give me 3 months of free subscription, since I reveal your bugs to you, at least I was the first to discover that version 25.4 is eating memory and I'm not alone in that trouble...

I am not alone.....

https://community.adobe.com/t5/premiere-pro-bugs/serious-issue-with-adobe-premiere-pro-after-the-lat...

I wish you all the best...

[R Neil Haugen]

I'm another user, you do understand that, right?

And I'm sorry you think anyone thinks you a guinea pig. I certainly don't. Since my other post, several days ago, a few other users have posted about memory issues. All any of us users can know at this time though is that it's a fairly small group, which at times majes it easier to suss out what is going on.

And I'm grateful to the users that have posted some awesome comments with tons of data. Posts like that are golden in troubleshooting.