HUGE memory leak - Mac Apple Silicon - Premiere Pro version 23.2

Thank you for your reply.
I understood that the first user's problem had been resolved, but as you can see it has been more than a year since other users have reported similar problems on this same subject, so it is clear that the error is not just a bug linked to a VST...
I also know that without a project and files your possibilities of action are limited, but they are even more so if you delete my (long) messages in which I try to explain in great detail what led me to the bug. I suggest you put them back online in order to possibly guide other users.
However, I was able to find what was causing my Mac's memory to explode, the plugin track was the right one. The culprit was the B Raw Studio plugin from Autokroma, which supports black magic raw video files. By dialoguing with Autokroma, they found a solution to the problem, by checking the “sync mode” box in the settings tab. Now it is working great.
I hope this answer will help other PP and ME users.
kind regards.

While there have been memory issues with those plugins, without a project, media and (important!) step-by-step instructions on how you can reliably reproduce the problem you're reporting, there's no way to know.

We are very cautioius updatinjg Prem pro in our office as it has halted production here in the past.

Have you checked out the Beta, @Luca37201893rrkd? It should be fixed there.

Take Care,
Kevin

Did you find a solution?

Still getting mem leaks here - No audio effects used and I'm only at RC stage. 

Hi all, 

Matt from the audio team here.  We have recently made a change in Premiere that will probably help many users hitting memory issues when working in projects with many clip based audio effects.  For some of our internal audio effects, we have reduced the memory footprint, which could lead to a lot lees memory consumption if the effects is used over and over in a sequence. 

This is currently in the public beta build since 24.5.0x14.  I want to reiterate that this is only for sequences that use a lot of our internal audio effects on clips.  Such as the Essential Sound workflows. Not every user will see an improvement since this change is only for audio effects.

In my case I had the editor send me a copy ( 130 MB ) of the Project ( from Premiere 2024 ). I opened it on a different Mac ... an older Intel mac rather than the M1 based one the editor had. Luckily the project opened and didn't imediataly crash.

From there I opened each Sequence one at a time ( there were well over two hundred ), did a selct all and used the "Remove Attributes" to delete all audio plug ins except the level pan settings and saved the project.  It took a couple of hours and by the end the Project was about 40MB. I sent this back to the editor and it opened no problem. They are back to work. No plug ins allowed.

The reason the plug in were in place was a stupid piece of advice from an idiotic "Sound Guy" ( I can say that 'cos I am one ...)  who told the editor to add a chain of audio processes ( an idiotic chain of 8 plugins btw ) to every clip using the "Paste Attributes" function! Ughhh....

As an aside I used my copy of the Project ( obviouly no media on line ) to convert to a Production. Essentailly it makes every Bin in the old  Project its own new Project all kept together in a Premiere Pane called a Production. The Pane actually refelcts a literal Project Folder on the storage. Way better for a big production  If moving from a Traditional Project to a Production it is proably best to rearrage the content within the Project... I feel that if all the Sequences were in a single Bin, these would still ed up in an single Production Project and the size problem might just move there! However I'm still experiementing  before I go and recommend it to anyone.

I've seen people expecting to open an entire long form project still in its components ( clips, titles, plug ins etc ) in a single Sequence. I dont think that is a reasonable expectation. Work in smaller sections, then render out finals as self contained single files. Then assemble these in a final sequence. The sequence will be long, but there wont be any plug ins required ( theroetically). For changes go back to the component sequences and re render. The process of "printing /mixing" down to sub-masters is totally standard in production. Once you get used to it you will be much happier....