Memory Leak with premiere project

[Scotty Slater]

I. Issue- Everytime I open a certain project, premiere uses all system ram. About 30% of the time it goes back down to regular levels after hitting the peak for a moment. Usually freezes premiere or crashes system.

II. Version- 24.1 I updated after I had this issue with 24.0, and premiere suggested I update.

III. OS- Windows 11 (64 bit)

IV. System Info 

      CPU- Ryzen 9 5900X 12 Core

      Ram-  2 sticks of 32GB 3200mz

      Graphics- RTX 3070 Ti

      Boot Drive- 970 EVO+ 2TB

      Footage Drive- (San Disk 1 TB extreme pro portable ssd) connected by usb c

V. Video Format- XVAC 4k: MP4 4k shot on sony a6300

VI. Workflow details

      Editing off of extreme disk pro, which I have had other issues with other drives, although I have not had any issues with this particular one.

Currently organizing and reviewing interviews, organizing using a different timeline for each interview. Working on about about 500 gigs of footage, split across 17 different timelines.

I have been working on the project for four days, and have just crossed my fingers and slammed my head into the wall until I got lucky and premiere would work. (Although, it seems to freeze if I let it run by itself for too long, so I have to try again; not the issue.)

It is a single cam sequence, and I am only reviewing one interview at a time, one clip at a time, about 30-40 gigs of footage per interview.

Have tried setting cap on memory resources, but memory still hits roof in about 10 seconds.

If Premiere fixes itself before it hits cap, it will work, if it goes over cap I have to reset.

VII. Steps to Reproduce- open project in premiere. see resource monitor to watch ram hit cap. 

VIII. Expected Result - To have premiere work.

IX. Actual Result-  Sometimes computer crashes, sometimes premiere acts normal, most of the time premiere is just frozen and memory is locked at around 40 gigs.

[Scotty Slater]

2 32 gig sticks, toltalling 64 gigs of ram. Excuse me.

[Scotty Slater]

Also, I am not using any kind of memory intensive effects. I have mirrored some of the timelines, but all the work I have done, and am currently doing at this stage is trimming, seperating, renaming and recoloring clips. This problem has been prevelant throughout this project. Last major project I work on in premiere was on 23.6 in November. 

[MyerPj]

Did you already do the basics like delete the cache? (Hold down shift as you start PP), then respond to the dialog. I went to look at your screen shot and got a project instead :-), I did open it and nothing happened. My machine (win11/pp24.1) it was using 7.6 gb of 64. All well, all the clips seem to have a flip on them. Why is that?

You can also open a new project and import that project into it, I just did it and have 7.3gb memory usage, with PP and Chrome open.

[Scotty Slater]

I have deleted the cache, and the startup worked, but the one after did not. About half of the interviews have them. The interviewer (me :clown_face:) was not consistent with which side they were on, so I changed some of them. 

When premiere doesn't bug out, it only uses about 20 gigs of ram for me.

I will try importing it into a new project though. Thanks for the tip!

[Bruce Bullis]

Hi Scotty,

Troubleshooting question: Does increasing the amount of RAM reserved for other applications (in PPro's Memory preferences), affect/improve the behavior? 

[Scotty Slater]

No it does not. It behaves exactly the same whether I give it 50 gigs or 20 gigs, and I tried a couple increments inbetween.

[Bruce Bullis]

Drat! Thanks for testing. 

[Michael Grenadier]

do you have the studio driver for the nvidia card installed?  Game driver can cause issues.

How large is your premiere project file? 

Do you have more than one timeline open at the same time?  Not always a good idea.   

Are you running any other programs concurrently?  If so... don't.  and see if that makes any difference.  

Also, gotta say, with a 4K mpeg format source, I strongly recommend using an all iframe proxy format.  

And about a year ago, had some serious issues with material shot on a sony camera (can't remember which one) and overriding the default colorspace to rec709 solved alot of issues.  

And creating a new windows user with administrator privileges and sometimes solve problems.

[Scotty Slater]

I do have the game driver installed. I will have to try changing it if I have more issues.

I have gotten it to more consistently boot up since I ported my work to a new project, although it still maxes out the ram to about 60 gigs (well past the cap I set), then falls to about 26 of usage (8 being background avergae). 

The premiere file is not very large. 

I will also try the overide if I have issues later down the line.

[Michael Grenadier]

Keep us posted

Michael Grenadier

[Personal info deleted by mod: forum rules!!]

[Scotty Slater]

I have used some of the work arounds as suggested, and it has been somewhat helpful, but all of a sudden premiere crashed and now I cant work on the project at all. I tried opening up other previous versions of the project, but those also crashed, which makes me think it is a drive issue. I am aware that samsung extreme ssds can be sketchy, so I will have to try that.

[Scotty Slater]

Switching to a new SSD has not helped unfortunatly. The only way I can work on the project is by spending the first 30 minutes of the day hoping it doesnt crash, then leaving the project open. I usually have to clear the media cache then spend a couple more tries of hoping it works. I can't seem to create a formula for success, it sometimes works and sometimes doesn't.

[Bruce Bullis]

[reached out to Scotty to get a non-opening project]

[Scotty Slater]

I am sorry. I don't understand. Would you like a current copy of the project I am working on? I haven't received a request to send a project somewhere.

[Bruce Bullis]

Yep!
[Deleted post with Scotty's email address]