Premiere Pro RAM usage skyrocketing

Did you end up figuring out what the culprit was? I am going through the same thing. I've been editing a feature documentary on an iMac Late 2015, 4.0QC, 32gb, Fusion Drive and have been fine until the past month when Premiere has been freaking out. The project file was getting bigger because we had more media, but it had been doing fine. I only have 32gb of memory, but it when Premiere was freezing and the pinwheel of death showed up the Activity Monitor showed it was using almost 48gb Memory and 42gb of Compressed Memory. I have yet to delete the media cache on my external drive, but I did call Apple and we cleaned the cache on the computer and wiped the disk, but it's still acting funky and very slow.

Having same issue here on Windows 10 machine. Turns out that, Warp Stabilizer and heavy resources FX are the culprit of why my RAM skyrocket even thought I have 32gb of rams.  I found out when I was using the Rolling Edit Tools and editing Lumetries on very large Adjustment layers.

Got to the point of rendering clips that use warp stabilizer as well of some other FX like denoising, After FX dynamic links, rolling shutter etc to reduce the lag and crashes that are caused by memory hog effects.

If I may suggest to Adobe, you have a wonderful program called Prelude to prepare clips for editing. Unfortunately it missing features that could be very helpful to reduce Premiere high memory stress by rendering primary effects like I mentioned above. That could help a lot to overcome these editing woes.

Hi julied,

Please let us know if you need more assistance.

Thanks,

Rameez

update: I have started on to another project (the very beginning of a feature, so only a small portion of the bins, clips and timelines that I will eventually have or had in my other project), and Premiere is cruising along with RAM usage hovering at no more than 8GB. The size of this project (let's call it project B) is about 20MB, while the size of project A (the one with the crazy RAM usage) is 40MB. Not using Luminetri scopes or anything on project A. I'm tempted to trash project A and start fresh, and just import the bins I am actively using and see what happens there (like I used to do with FCP). I will post my results!

Thanks everyone who took the time to read this and post a suggestion!

I just came across this:  Apple Releases macOS Sierra 10.12.3 With Graphics Fixes for 2016 MacBook Pro

Yeah, trashing your cache or Preferences is unlikely to help this sort of scenario. Memory leaks can be really tricky. I'd go as far as deleting and re-installing Premiere entirely (really, not hard these days. Just a few clicks and a few minutes). But just to be safe, delete Preferences and the Cache between deleting and re-installing.

Maaaaaybe also make sure your CUDA driver is up to date, but Im not convinced that's the issue. But always worth doing anyway.

You said you have 13GB reserved for Premiere and yet it's using 18-24? Are you sure you haven't reserved 13GB for OTHER applications? That's the way the setting is worded in Preferences. Just curious there.