Premiere Pro Memory Leak Auto Detect Log Footage

@jamieclarke I am not currently using any third party plugins in my workflow, at this stage. Everything so far has been done using premiere and a basic workflow.  I do have Excalibur installed and use the shortcut to grab a quick cross dissolve or dip to black, but that's it.

I have tried having the activity monitor open to see when things are jumping, and I need to do more precise tests. Currently my specilation is that this has something to do with multicam source sequences for the project, as I might have noticed a jump when changing from normal composite view in the program monitor to multicam view. That said, I haven't been able to really test this, as I need multicam view in order to edit this film, but considering my other current projects aren't using multicam source sequences and aren't experiencing this issue, that's a current guess. I will try and replicate when I am back home.

@bbb_999 Originally I had a default setting for memory allocated to other programs, meaning premiere would use most of it, considering that's where I spend most of my time. I did change this to 32GB, so premiere uses half and other programs use half, but there was no significant change, if at all. 

In PPro's Memory prefs, how much RAM are you reserving for other processes? 

Do you see a change in behavior, if you reserve more RAM for other processes? 

Hi @mattiasalegro -  Thanks for submitting your bug report. We need a few more details to try to help with the issue.

Are you using any third party plugins or third party panels in your workflow?

Can you open your activity monitor and provide reproducible steps on when you see the memory going up?
Sorry for the frustration.

@MyerPj I have deleted the cache. I can't create a new project and import the old one, as I am in a productions workflow with the entire thing broken up into separate projects, so unsure how to do that using productions. 

I'll try your hail mary. Another hail mary I was given was moving the media cache to an external drive as opposed to internal.

@Kevin-Monahan I have already migrated the project to a Productions workflow, as mentioned above. Raw footage is not in the same project as my working sequence. Even scenes are split up into different projects so I'm not opening scenes I'm not working on. I assume moving to a productions workflow achieves the same results as creating a new project and importing the old one, as now that everything is broken up into separate projects I am not using the old project anymore and have created entire new ones. Otherwise I wouldn't know how to import everything to a new project now that I'm in a productions workflow. 

Clearing user prefs, deleting the cache, open new project and IMPORT in the current one. If you open Premiere holding down shift, you'll see some options you can try.

These are just basics, so hope you can find it.

Oh, a hail mary is in Preferences/Audio Hardware, and setting the Default Input to No Input.

Hi @mattiasalegro,

I read your note. It sounds like you are having a problem with your current project and memory leaks. What you might try is creating a new project and importing the old one into the new one. That can "rewire" the project for success. I find that these memory leaks occur most often in large projects carried across major new versions. The advice is to remain on a version throughout the life of a large project, like a feature. Another precaution is to use the Productions workflow where a large project is divided up into smaller "sub" projects. This leads to a more stable production environment as the project containing sequences do not also have to have the clips in the same project, keeping it running more reliably and creating a more stable workflow. I hope the advice helps. Let the community know how it goes. Thx, ^KM