Premiere Pro Memory Leak Auto Detect Log Footage

Hi @mattiasalegro - There is a potential fix in beta version 25.2.0 build 124 and higher.  Can you try it out and let us know if this helps your issue?

updating status to Acknowledged

Hi @mattiasalegro - Can you confirm which version of Premiere you are working in? and which specific version of mac you are on.  What type of footage are you seeing this with?  Can you send your edit project to jamiec@adobe.com

It seems that Auto-Detect Log Footage in conjunction with multicam source sequences has caused the memory leakage. While both are fine on their own, I'm experiencing stable memory when I turn off Auto-Detect Log Footage, and at least with a project this size, in premiere 25, that seems to be the correct answer.

That said, even though I have turned off the function, some footage still looks like log, and some looks like color corrected rec.709. This might be an issue with productions vs single project, in that I am unsure if I need to turn it off on every project within the production or not. Even with the function checked, sometimes there's double the contrast and saturation on multicam view, as if the LUT/calculation is being applied twice. Either way, turning it off has worked, it's stable now so I'm not worried about it. 

@jamieclarke I have now been working for a few hours, and after turning off the "auto detect log footage" function in production settings, this seems to have solved the issue. Premiere is no longer leaking tons of memory and activity monitor shows it as relatively stable. At the very least, I have gone a couple hours without crashing or warnings.

@jamieclarke @bbb_999 Did some further tests based on my assumptions. Not sure if it was perfect, but here's what I found:
- Worked on the project for 30 minutes while in regular composite view on the program monitor.  The activity monitor showed Premiere getting as high as ~18GB, but never went above 19-20GB (as far as I could tell.). Mostly it hovered between 10-14GB, with the occasional jump. After 10 minutes I also allotted more memory usage (the maximum) in premiere leaving only 6GB for other programs. I saw no significant jumps in memory.
- After 30 minutes of working in composite view, I switched to multicam view. There was an immediate dip, to about 6GB, and then after a minute and a half of working it went above 20GB.
- It slowly climbed with each edit I made (I should note I'm doing pancaked timelines, where I'm pulling from my selects on one timeline and dragging to my edit timeline. Though for this particular scene there is only the two sequences, plus 18 multicam sources open. Everything else is closed in another project.)
- after an hour of working it finally gave me the "too much application memory" warning, where I saved and closed premiere. I think there was a time where it stalled out at 44GB, and then again at 70-80GB for a while. I tried to do a video recording but I unfortunately didn't realize that the text in the activity monitor was too small, so it's basically unreadable. 
- Another thing I tried was to turn off "auto-detect log footage" in the production settings, and while I cannot be sure, I think this allowed the memory issues to stabilize at times. While memory usage never went down, it also didn't go up significantly. Then when I turned auto-detect log footage back on, I did also see some more jumps with edits. Again, all this in multi-cam view. (Detect log footage was on the entire time while in composite view, but again premiere seemed to work normally.) 
- No effects or plugins used. Simple making cuts, dragging to a sequence, and every now and then adding a dissolve. I was surprised that the program didn't fail sooner, but that's possibly due to turning off auto-detect log footage. While memory usage was still high, it might have kept it from jumping sooner. Sorry if this also throws a wrench into things. I could always try the test again and see if working with it off, while in multicam view, results in the same or at least how much time goes by before there's significant increase in memory.

>My intention is not to blame premiere but only solve the issue...

That comes through, in your posts; thanks!

Happy to help further, when you've had a chance to explore further.

@bbb_999 I would say that it is a gradual upward slope rather than a step change in memory, when switching to multicam view. Again, I haven't been able to fully test this, but the gradual, slow consuming of memory has been present no matter what I do, with this specific project, and the main difference being that is uses multicam source sequences.

I understand this is not intended behavior, and have never encountered this before, leading me to mark this as a bug. I am not claiming that the multicam is heavy, nor do I think it's a particularly heavy project (I have another that uses Red Raw footage that I haven't noticed any problems like this, though it has been a while since I opened it, and not since I started having memory leakage.) My intention is not to blame premiere but only solve the issue or give as much info so as to find the culprit if this bug. 

Good to know. 

Many of the processes spawned by PPro usage, are not necessarily owned by PPro (as far as the OS is concerned); consequently, if you give PPro too much memory, it can end up 'fighting with itself' for memory. 

Yes, multi-cam is 'heavy', but PPro should be able to survive cutting multicam sequences. From a symptomatic perspective, enabling multicam should generate a 'step change' in memory usage; a leak should be more gradual, showing an upward slope in memory usage, rather than one big step when you turn on multicam mode.