Question Premiere Pro is using a lot of RAM ?

[tridibeshdashingggg]

CPU: Ryzen 7 2700X
GPU: 6750XT Challenger Pro
RAM: 24GB
HDD free space 589GB
Premiere Pro Virsion 24.4

I recently recorded 1 hour and 34 mins long Hellblade 2 gameplay using AMD adrenaline recorder (at 3200×1800 res) and wanted to edit that in premiere pro with only lumetri colour as an effect and simple cuts.

My export settings are, h.264, resolution 3840×2160 (i scaled it from 3200×1800), hardware encoding, render at max depth and quality, level 5.2. After that I hit export.

Premiere Pro started eating RAM at the rate of 1% every 5-10 seconds and soon it's exceeding the allocated RAM level of 21GB. After a few minutes it crashes. The first crash error was "bad allocation while creating disk"....... I deleted media cache and tried to export but same thing again.

I tried changing the page file settings for my D drive by turning it on and setting to "system managed" and then i hit export.....after 80% crashed again with error code -1609629690.

It's never like i haven't exported long form gameplay videos using premiere pro but this time I can't do it no matter what i try I don't know why.

One other peculiar thing is, while on the export panel the RAM usage was rising gradually too when i didn't even touch the "export" button . And every time I minimise and maximize the task manager the RAM usage drops down from 39% to 20% all of a sudden. But this trick didn't work during export, RAM usage kept rising.

Plus, after hitting "ok" button on the crash error pop up the export gets cancelled but the RAM usage stays stuck at the last peak usage Percentage. It only drops when i close premiere completely.


Any solution for this?

 

[RealBeast]

Your hardware is really not adequate to do long 4K renders. There are some potential work-arounds that are discussed in THIS thread by Toxos on using proxy workflows that might work for you.

 

[tridibeshdashingggg]

Your hardware is really not adequate to do long 4K renders. There are some potential work-arounds that are discussed in THIS thread by Toxos on using proxy workflows that might work for you.

I've done exporting like this previously and it worked great, plus i think it's a bug. Because even when the exporting stops, ram usage stays locked on last usage Percentage even when i delete the main video file from my har drive, and delete the sequence from timeline.

And at this perticular time no other apps can be used because the pc goes extremely slow that it auto closes browsers or file explorer if i try to open them..... Only way to get rid of this is completely closing premiere pro.

 

[Ralston18]

Noted:

"I've done exporting like this previously and it worked great, plus i think it's a bug."

Consider that things have changed and for some reason (e.g, less disk space available) the system and software has hit some threshold value that is now causing the problem.

I will add some suggestions:

Look in Reliability History/Monitor and Event Viewer for error codes, warnings, or even informational events that were captured just before or at the time of the crashes.

Also use Task Manager (noted that you have used Task Manager) and Resource Monitor to observe system performance while rendering. Use both tools but only one tool at a time.

Objective simply to observe system resources: what resources are being used (you mentioned RAM), to what extent any given resource is being used, and what is using that resource - adrenaline recorder, Premier Pro...?

Very likely per @RealBeast your hardware is now no longer up to the task of lengthy renders.

May have been marginal in some manner to begin with.

Immediate actions you can take:

Run "dism" and "sfc /scannow"

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

Manually download, reinstall and reconfigure Premier Pro. There may have been a quiet fix to address some bug....

 

[tridibeshdashingggg]

Noted:

"I've done exporting like this previously and it worked great, plus i think it's a bug."

Consider that things have changed and for some reason (e.g, less disk space available) the system and software has hit some threshold value that is now causing the problem.

I will add some suggestions:

Look in Reliability History/Monitor and Event Viewer for error codes, warnings, or even informational events that were captured just before or at the time of the crashes.

Also use Task Manager (noted that you have used Task Manager) and Resource Monitor to observe system performance while rendering. Use both tools but only one tool at a time.

Objective simply to observe system resources: what resources are being used (you mentioned RAM), to what extent any given resource is being used, and what is using that resource - adrenaline recorder, Premier Pro...?

Very likely per @RealBeast your hardware is now no longer up to the task of lengthy renders.

May have been marginal in some manner to begin with.

Immediate actions you can take:

Run "dism" and "sfc /scannow"

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

Manually download, reinstall and reconfigure Premier Pro. There may have been a quiet fix to address some bug...

I fixed it.


I thought switching to windows 11 was causing this so i installed Windows 10 but the problem persists.

I recorded another 1.34 hours long video but this time I recorded it in three parts each of them are 30mins long.

I used adjustment layers to add effects rather than adding them directly to the sequence. I turned on page file on my D drive and set it to "system managed".

After that everything worked fine, and the process ended within 1 hour 8 mins of time.