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

How did you do the audio plugin cleaning and what is the impact of this on the project?

Happening with my 22mb project file so project file size does not seem to be the culprit. It does seem like it started happening when I imported a sequence from another project, and that project was created with earlier version of Pr? Although, I can't confirm this. So far I found that if I open an earlier version of the project file, it is stable, but my latest project file is not. Went back to earlier version of Pr 24, but that didn't seem to make a difference. Haven't tried Pr 23 yet because I won't be able to open my recent project file anyway.

I'm having this same issue but with a fresh new project, all I did was just drop in one video and I try to detect scene cuts, after about one third of it Analyzing Clips, it seems to have this problem occur. So my guess this isn't a big project size problem, any idea from anyone what this might be or what the fix might be?
Thanks in advance!

Hey @Remote Index ,

well, regarding Warp stabilizers, dunno what is now normal and "a lot" when we

talk about projects exceeding 100 MB. Warp stabilizers seem to increse the size by 1-2 MB,

where sequences go 10-15MB or more... If project size should be around 20MB, I guess Warp is a lot...

Regarding "productions", can't really discuss in detail the inconveniences since I haven't fully tried to work

in such a way, my comment was more reffering to previous comments here, suggesting to split the project into

smaller sequences. When working on a feature length of any kind, it is ludicrous not to have an entire film in the timeline, especially once past the first assembly. But I guess to have various versions of the cut in several projects via production folder is actually wise, nevertheless to rip the film off of it's full one-sequence continuity is crazy, weather it be 90 minutes or 4 hours. Dunno, maybe I understood some of the previous comments suggesting "productions" in a wrong way- like I said, haven't fully dived into such a workflow...

Cheers,

Hello Neda Fustimu,

I had a couple of notes on your post that I thought worth sharing:

"also I had a lot of warp stabilizers but they don't seem to create such an issue as sequences."

I'll just note that in my experience, each instance of warp stabilizer that you add a project drastically affects the project size - my experience is that adding warp stabilizers in Premiere Pro is a sure path to project bloat. Currently, I do all stabilizing via dynamic links to After Effects as a workaround.

"This new solution they offer, productions, is also inconvinient for some workflow"

My experience is that prouctions is a pretty frictionless change to workflow, and even adds some convenience and definitely addresses the issue of project size and resultant PPro slowdown. I'd be interested to hear what sort of problems or inconveniences it creates for you.

R.

Hello,

I'm using Premiere Pro v24.3.0 (Build 59) on a Mac Pro 7.1 (3.3 GHz 12 core with 192 GB of ram on an AMD Radeon RX 6900 XT & Radeon Pro 580X) and also getting crazy memory leaks while rendering out a clip... 328GB after 10 minutes and then a crash is followed. I was using Neat Video 5.6.1 (SR) Pro plug-in on a 1 minute clip for noise reduction.

Is there a solution for this? Any idea's?

Many thanks,
Radek

And to be fair, despite my justified frustration, @Mitch W was most helpful to indicate the source of the problem, much appreciated and thanks!

Hello everybody! Needless to say, I've been having the same agonizing problem that many of you experienced. I'm editing a 2,5 hour fiction film, and the further I went along in the proccess, the more memory issue appeared, crashed the programe, destroyed 15 sometimes 30 minutes of my work. I tried emptying the hard drive- nothing, deleting all the cash- eventually nothing, there was no rule when the crash would happen, could be literally anything- just moving the cursor. As the project became bigger and bigger(reached 150MB in the end), I started experiencing this issue in the very opening of the project. Lost three days of work now due to Premiere not being able to even allow me to start working after opening. So, FINALLY I FOUND A SOLUTION! Regardless of that, this is utterly embarrasing from Adobe and unprofessional.

As it turns out, I had a lot of sequences in the project(which is damn normal when editing a feature). I had to delete 70 percent of the sequences which reduced the project size by 30 percent, and now it opens the project within seconds and saves it as fast- which was not the case before. So far, runs smootly, and also I had a lot of warp stabilizers but they don't seem to create such an issue as sequences. Now the project is 100MB and as I remember the issue started to appear drastically when it went over 120MB. Since I have weeks now to finish the film, late overdue, this solution is more then satisfactory, but nevertheless- the fact that Adobe silently suggests that the project cannot go over 100MB, hence one cannot have previous sequences and even worse- should split the sequences into smaller bits is literally nonsense when editing a feature film of any kind. If this needs to be explained to Adobe, well then... obviously, since I've been desperately searching for a solution for months and have seen lots of people with this isue, they don't seem to care about fixing this- so relocating to DaVinci seems to be the best move. This new solution they offer, productions, is also inconvinient for some workflow- although could prevent this issue from happening I guess. All in all, reduce the project size as much as possible, delete sequences or whatever you disover to be the burden on this fragile app, wrap the work and voila! It'd be nice from Adobe to state this as factual, rather then beating around the bush... Hope I helped! Cheers,

Hi Mitch ( and anyone else interested!)

I'm happy to report that once I cleared all the audio plug ins out of the misbehaving Project from all of the sequences within

by opening it on an Intel Mac, ( no media storage attached),  the Apple Silicon machine was able to open it and the editor is back in busness ... albeit with a meeting on the calendar with me to discuss workflow going forward! 

Takeaway - work on large projects ( greater than 10 miniutes) in sections, dont layer on uneccessary processing ( FX, Color, Audio ) unitl you need to, and when you do make another project for it! 

It is quite possible our issue isn't what others are experieencing.. but THANKS SO MUCH to the Adobe folks for chiming in and pointing me in the right direction. Super appreciated.

best

lee

Hi Remote,

Excellent point and good call out! We just had a discussion around this, and we'll see if we can start providing some useful guidance in our documentation in regard to project size. In the meantime, here's some detail that may help. The actual project size as measured in MB is more of a bellwether than anything else. There are multiple factors to consider here including installed RAM, disk speed, and CPU clock speed. A "large" project is going to be different for everyone. That said, anytime I see a project that's larger than 100MB then I start to become concerned. The size itself doesn't necessarily mean there are going to be performance issues, but it's a decent indicator. More than the actual project size, users should start to pay attention when it takes more than 30 seconds to open a project. That time doesn't include locating media, locating preview files, or building any needed cache files, but just opening the project file itself. If we're struggling to open the project file, that's an indicator that you should take notice of. We'll start an internal discussion on how best to present this info in an easily understandable and usable form in our documentation. We think you had a pretty good idea there and in hindsight it seems like an obvious omission.

Regardless of your current project status, I would encourage you to start exploring Premiere Pro productions just to understand how it might benefit your workflow in other ways beyond improving your overall large project performance. Having access to additional tools is never a bad thing.