Memory leak - Mac Apple Silicon - Premiere Pro version 23.2

[Luca37201893rrkd]

I don't have any VST.

I use only 3 plugins:

- BRAW Studio

- Neat Video 

- Cinema Grade

But none were used in the project when the problem appeared. 
Could it come from one of them? What do you think? I would like to point out that I have been using these plugins for several years without any bug.

Mod note: The title of this bug report has been changed slightly.

[Luca37201893rrkd]

Hey there @Luca37201893rrkd,

Thanks for the information. That is much appreciated. I have similar Macs (hey, Cupertino is my home town!) and do not experience such weirdness (I am an editor too!)

The only difference between our systems is our different workflows and media (I use mainly H.264/HEVC/ProRes LT).

Can you try a brand new test project without using BRAW media? BRAW is not a supported format and, as you know, relies upon a third-party plug-in for that format to function inside

[Luca37201893rrkd]

Hi Kevin !

Thank you for your answer.
Unfortunately I am also a victim of the Premiere Pro and Media Encoder bug. I just tried the beta versions and it's not fixed.
I will try to describe the problem, how it happened and how it persists, to give you something to think about.
The bug first appeared when I updated Adobe software to version 2024 on my Mac Mini M1 16gb Ram 512gb SSD.
I mainly film live music in multicam with BMPCC4k. My rushes are often more than 1 hour long, in constant quality Q3 braw, and the bug appeared the first time when I was generating the proxies of the 6 cameras that I had used for a concert (Prores low quality proxy).
So it wasn't a very complicated project at all!
I opened a new project, imported the 6 video files, started creating proxies with ME, and 2/3 of the way through the generation of the first proxy, my memory was full.
I didn't have time to think much to find a solution because the client was in a hurry, so without thinking I reinstalled the 2023 versions, and everything was back to normal. This was my first encounter with the bug.
I then worked for several months with the 2023 versions without problem.
Last week I decided to change computers, being a little limited by the Mac mini, I bought a second-hand Mac Studio M1 Max 32gb Ram and 512gb SSD.
After installing the latest versions of the Adobe software that I use (photoshop, photoshop beta, lightroom, after effects, PP, ME, ID, Acrobat), I wanted to export a very simple video again. It's 5 hours of video taken from a single camera that filmed a theater festival over a weekend.
I just created a sequence by putting the rushes one after the other, without any editing or color correction, and I exported everything in 720p. Normally everything should go well, and unfortunately when I was halfway through the export with ME, the ram had reached 120gb and the computer crashed.
Since several days I have been trying to find a solution by myself, I have tried more than 7 versions of PP and ME, from 2023 and 2024, and I still have the bug.
I also tried to uninstall creative cloud, start with the Intel versions, use different versions of PP and ME, basically everything I found on the internet, but the bug unfortunately does not disappear.
I still give details of what I was able to spot:
In the activity monitor, we can see that the memory consumption increases little by little without stopping until the computer freezes (up to 120GB in my case), but in the small graph at the bottom "pressure on the memory", the consumption gradually increases to 26gb (over 32gb) then stabilizes in yellow and stay around 26gb (so it looks normal here!). When it crashes, it turns red but doesn't reach the maximum (red at 26gb). As if the Mac couldn't see that the memory was consumed.
For the processor it's the same, ME consumes 900% of the processor, but on the graph below, it is not saturated.
Does the bug only occur with used computers? Could this be linked to the Adobe account (very strange that this happens to me on 2 different Macs).
I sincerely hope that you will be able to find a solution, I will be available for more details.
Thank you so much and kind regards from Switzerland.
Eric 

[Kevin-Monahan]

Hello @Luca37201893rrkd,

Thanks for the bug report. Please give the team your specs. See: How do I write a bug report?

I hope we can help you.

Thanks,
Kevin

[Kevin-Monahan]

Hi @Luca37201893rrkd,

You can also experience this issue with large projects with many clips and sequences. Could that be your issue? Or does this happen with small projects too? Let the team know more info.

Thanks,
Kevin

[Kevin-Monahan]

Hey there @Luca37201893rrkd,

Thanks for the information. That is much appreciated. I have similar Macs (hey, Cupertino is my home town!) and do not experience such weirdness (I am an editor too!)

The only difference between our systems is our different workflows and media (I use mainly H.264/HEVC/ProRes LT).

Can you try a brand new test project without using BRAW media? BRAW is not a supported format and, as you know, relies upon a third-party plug-in for that format to function inside the application. Your media is my suspicion since it is unsupported, and things can go wrong when your workflow depends on third-party tools and plug-ins.

It sounds like you tried to create ProRes proxies but ran out of space. Gain some space and retry that experiment. If I were in your situation, that is the first test I would try. Let me know if it works or not.

I am a firm believer in avoiding camera originals to edit with. It is a much better idea to transcode all footage to an editing codec instead. Everything goes a lot smoother after you do that.

Thanks,
Kevin

[Kevin-Monahan]

Hey there @Luca37201893rrkd,

Thanks for the information. That is much appreciated. I have similar Macs (hey, Cupertino is my home town!) and do not experience such weirdness (I am an editor too!)

The only difference between our systems is our different workflows and media (I use mainly H.264/HEVC/ProRes LT).

Can you try a brand new test project without using BRAW media? BRAW is not a supported format and, as you know, relies upon a third-party plug-in for that format to function inside the application. Your media is my suspicion since it is unsupported, and things can go wrong when your workflow depends on third-party tools and plug-ins.

It sounds like you tried to create ProRes proxies but ran out of space. Gain some space and retry that experiment. If I were in your situation, that is the first test I would try. Let me know if it works or not.

I am a firm believer in avoiding camera originals to edit with. It is a much better idea to transcode all footage to an editing codec instead. Everything goes a lot smoother after you do that.

Thanks,
Kevin

[jmanrech]

Hi @Kevin-Monahan It seems I'm having this memory leak issue with large projects. I'm on Premiere 24.3.0

Do you have any recommendations what to do with these projects?

[Kevin-Monahan]

Hey @jmanrech,

When it comes to stability on the project and performance level, I've had great success with larger personal projects using Productions. Are you familiar with that feature?

Thanks,
Kevin

[jmanrech]

@Kevin-Monahan I know of productions, but I've never actually used it. Is there a good place to start to learn about it - I share projects with other editors so I know it can be pretty useful but haven't taken the leap out of fear of having the project files getting messy.

[Kevin-Monahan]

Check this out, @jmanrech: https://helpx.adobe.com/premiere-pro/using/long-form-episodic-best-practices.html

Kevin

[jmanrech]

Cool, thanks Kevin!

[jmanrech]

Hey @Kevin-Monahan , I tried using productions for this project to split it into small sessions and I'm still having the same issues. I've cleared my media cache, updated to the latest version, unistalled, reinstalled, restarted. I can't even make proxies for some of these files without it freezing. Any other thoughts on what I can try? Let me know if you need my specs or any other info.

[Kevin-Monahan]

Hi @jmanrech,

Thanks for the reply. Sorry, the suggested fix did not work with your current production. The team might need more information about your hardware and media. See, How do I write a bug report?

I hope we can help you with more details about your case.

Thanks,
Kevin