Premiere Pro CC2015 using too much RAM?

[Guest]

Been using CC2015 for a couple of days now and notice it's using more RAM than it should, according to settings in preferences. After a few minutes of SD material playback it's used up almost all RAM in my system making it virtually unable to operate. Ranging from Blackmagic 480i/p AVIs to Blackmagic 1080p AVIs, XDCAM EX files and AVID DNxHD/Meridien QuickTimes. Does anyone notice anything similar?

Cheers!

Here are my settings:

And my taskmgr:

Specs are as follows:

Win7 Pro 64bit SP1

HP Z800 with dual Xeon X5680 @ 3.33GHz

48GB DDR3 RAM

300GB SAS system Drive

32TB SAS RAID on 16x2 TB Hard Drives

4GB Geforce GTX 970

Premiere Pro CC2015

[donalb2505807]

I am having the same issue. I however only have 12.8 GB RAM dedicated for Premiere, but it is using ~11 of it sitting idle. I can hardly do any playback or edit.

[Ann Bens]

First of all I would set Optimize Render for: Performance.

The only time you will have to set it to Memory is when Premiere gives an error message saying its Low on Memory.

This might help:

Close Premiere, go to Windows/Users/User/Appdata/Roaming/Adobe/Premiere Pro and delete the 9.0 folder.

Restart Premier.

[Guest]

Hi Ann,

Thanks for your suggestions. I had originally tried optimize for performance, but switched to memory when I had noticed the problem. Deleting the 9.0 folder did not help either. However, it seems I am only getting this problem with footage running at 23.976 fps, but all ok at 29.97. Weird!

[Movieboy711]

Yeah, I'm having the same issue as well on Premiere 2015. I am working with regular HD footage, at 29.97 fps, and I noticed that premiere is using 10GB of Ram. Usually, this same footage would not use no more than 3GB with Premiere 2014.

[donalb2505807]

Same issues:  Re: RAM Ramp up during playback after PPro CC 2015 Upgrade

[Ann Bens]

Try this: Documents / Adobe / Premiere Pro and delete the 9.0 folder.

[donalb2505807]

Tried that, but does not seem to make any difference 😕

[Movieboy711 · Accepted solution]

Actually, someone on reddit pointed out that the memory leak seems to be coming from Luminatri Scopes. I can confirm this. Whenever I have the scopes window open, my RAM usuage starts to sky-rocket without stopping. As soon as I close it, the RAM usage goes back to normal.

[excited_Genie16B8]

I can't duplicate this on Windows 8.1 Pro.  The memory usage stays constant when playing back a sequence with the Lumetri scopes open.

[Guest]

Thanks, Movieboy711!

That does seem to help quite a bit. But, RAM is still going up, just not at all as fast. I can now run about an hour before restarting, as opposed to 5 minutes previously.

[Kevin-Monahan]

Hi Magnus,

Yes, we did find memory problems with Lumetri Scopes. We're working on the issue now. File a bug here: http://adobe.ly/ReportBug

Thanks,

Kevin

[Guest]

Done!

Thanks, Kevin!

[jasonjam]

Hi Kevin,

I'm having the same memory issue as Magnus. Has Adobe started to fix the issue?

Jason

[Vinay Dwivedi]

Hi Jason,

Yes the issue has been reported and is worked upon.

//Vinay

[bastianf89726742]

Hello,

I'm still experiencing this issue.. have i missed something? It works fine as long is I dont use the lightning effects, but i really need them for some of my projects.. im using the latest version of Premiere CC15.

[claudioparoli]

Vinay I'm having the same issue of Premiere Pro CC2015 (v9.0.2 (6) build) grinding to a halt after every single edit.

Note that I have all Lumetri off and extremely simple edits on a timeline running only 1080i/50 XDCAM EX footage while source & program monitors both run at 1/4 resolution.

The problem does not seem to be there if I cut into the timeline material from the source monitor. But every time I use the selection tool (V) or the rolling tool (N) directly on the timeline, PP grinds to a halt for several minutes. I can still save but do nothing else. I've tried deleting the 9.0 folder - no difference.

My system is rather old but adequate for non time-crucial editing, an i7 290 with 12Gb of RAM, with both PP and the OS (Windows 10 Technical Preview build 10532) running on a Samsung 840/256.

PP does not report any memory problem. On performing an edit on the timeline, Task Manager will report some 50%+ used. PP is reported using about 3.5Gb of RAM which then over the next 3-4 minutes drops to around 1.5Gb with PP idling. PP has 7GB of dedicated RAM when editing. I've experimented with more or less RAM - no apparent effect.

Any suggestions, Vinay?

Thanks

[Ann Bens]

Just a wild guess: Turn off : Composite Preview during Trim (wrench timeline)

[tylerh66980855]

Good lord, is this fixed yet? I am about to be fired. I have a deadline that has already passed. The only way that it seems I could possibly fix this is to, what. Re-color everything in a different program? I used lumetri because YOU provided it to work with YOUR program. Now I cannot render at all without running out of memory and Adobe automatically killing the process. I do not have time to re-color everything.

I will likely be let go on Monday, and it will be because Adobe doesn't seem to care about the product they put out.

[IanOChambers]

Same!!! What the hell is going on Adobe? Fix this!

[IanOChambers]

Thank god I have Final Cut Pro. Adobe you suck.

[Kevin-Monahan]

Same!!! What the hell is going on Adobe? Fix this!

Hi Ian,

Sorry for your trouble. Please work with support here.

Adobe you suck.

If you have complaints about the product, it is better to file a bug report. Most employees in charge of quality will read the bug report but not the forum, which is largely user-to-user based.

Thanks,

Kevin

[bastianf89726742]

The Support just brought me to this thread and closed the ticket and i already reported my bug, but alright I'll try again.

[Kevin-Monahan]

Hi Tyler,

Now I cannot render at all without running out of memory and Adobe automatically killing the process. I do not have time to re-color everything.

Any time you have trouble, please work with support here.

Thanks,

Kevin

[tylerh66980855]

This is super insulting. Seriously. You are being super insulting. This is probably because you have been ordered to be. Please tell the people making you be super insulting that you're being super insulting. Somebody doesn't know they are being super insulting, but you're being super insulting.

To reiterate, you are being super insulting.

Adobe messed up REALLY BAD. There are dozens of people I know personally that have had their ability to do their jobs entirely erased by your bafflingly idiotic decision to strip out multicore processing without telling anyone, and moreover that ADOBE has a product PUT OUT BY ADOBE that BREAKS ADOBE. This is a really bad mess up. You have messed up really bad. I am repeating myself often because YOU PEOPLE AREN'T LISTENING TO US.

Why are you being super insulting? Because YOU messed up. This isn't us. This is what your company did. We were fine until you made these errors. How could you STOP being super insulting? By admitting it. By apologizing. By announcing an actual timetable to correct these mistakes.

Adobe's lumetri color doesn't work to the point where if I use it your advise is "don't use it." This is ridiculous. I have lost a job because of you. Because of YOU, ADOBE. Not you, Kevin Monahan, who is being super insulting, but your company. You are going to lose me forever as a customer because you keep making this seem like it's our fault, when you messed up HORRIDLY. This is when an apology is called for, a massive "holy crap we made a really bad mistake please bare with us" and then actually fix it. It's been MONTHS since these problems started.

Stop being super insulting. Start acting like an adult company. I cannot believe your company's behavior.