Skip to main content
Known Participant
Mar 15, 2023 2:04 PM UTC
Answered

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

I have an issue with the latest version of premiere working fine but progressivley getting slower, then filling all available ram and disk swap, I get a memory error on mac with premiere pro usung in excess of 100GB editing standard 4K footage, footage that never used to have issues until this version.

 

My system 

Macbook pro 16 inch, 32`gb ram M1 Max

latest OS (13.2.1 (22D68))

Premiere 23.2

 

Its happened on multiple projects, some new some old.

 

I've had to revert to the previous version for my own sanity.

 

Does anyone else have this issue?

This topic is closed to new replies. Start a new post to keep the conversation going.
Bruce Bullis
Bruce BullisCorrect answer
Legend
Jun 4, 2024 8:55 PM UTC

The original issue that generated this thread, has been fixed. It was related to memory usage around VST plugins. 

[I'm not discounting the possibility that you're encountering a different issue...]

Do you have third party VST plugins installed?

149 replies

mickpeninsulaTV
Known Participant
Oct 19, 2023 7:04 PM UTC

Did anyone get an update or a fix >

 

 

My M1 max pro 2022 is getting it every project now.

 

No matter what SSD or drive I'm using...  Really frustrating...

Translate
Participant
Sep 27, 2023 4:41 PM UTC

I have this exact issue with my RAM usage jumping to around 120GB give or take almost exclusively when I am relinking footage. I work with assistant editors and when the project comes to me, relinking the footage is what causes the memory leak it seems. 

2021 MPB M1 Max, 64GB Ram, 2TB SSD

Translate
Participating Frequently
Sep 17, 2023 2:31 PM UTC

I agree.  Most of the memory leak issues happened while using Lumetri.  This sucks, because how else are we supposed to grade if not with the native color tools?  Bring back Speedgrade please.

Translate
Participant
Sep 17, 2023 9:58 AM UTC

Roughly half a year ago I began having this problem and when I did a search I was led to believe that the problem was highly associated with Lumetri Color effect. I stopped using it and resorting to Boris FX 3-Way Color Grade. 

Somewhere down the line I discontinued my subscription to Continuum and no longer had the Color Grade effect that came with. 

Ever since I stopped using Lumetri Color, the problem hasn't occurred. In the past 2 months I've been tackling heavier projects in VFX.

 

 

I work on a MacBook Pro M1 Pro , 16GB 512SSD. I regularly empty the disk cache for both PrPro & AE at the end of every session. I work in heavy VFX but unfortunately even with proxies my laptop can be pretty slow for my projects. So I resort to keep up extremely well on maintaince and the laptop itself always has about 300-350GB of available space at any given moment. I use an external hard drive for everything excluding Disk Cashe & Adobe Applications. 

When it first started happening I took in account that my favorite plugin that I use is Twitch from Video Copilot and I'm aware it's not MFR compatible. I used to think that was the issue, however, it didn't happen on a recent project that used the plugin quite a bit. 

I still use Sapphire FX from Boris FX and always have. Although Sapphire is more geared to VFX rather than Image Restoration, and doesn't have a "color grade" tool or effect, it doesn't have an effect called "ColorFuse" where you can combine up to 3 LUTs and set the strength of each on a scale of 0-1. 

For a majority of the time since I stopped using Lumetri Color, I relied heavily on using a combination of 3 LUTs from ColorFuse. Boris FX offers thousands of presets and their customizability has always been the key reason I use them. So ColorFuse often would suffice for any project that didn't need very specific correction of tedious grading. 

Today, I opened up a short film project. A personal project of mine. I spent a good 7-8 hours straight Rotoscoping with RotoBrush 3.0 in AE Beta. Unfortunately, my favorite plugin Twitch needs to open AE using Rosetta. So when the bulk of my edit was done, I resorted to nesting the parts of clips that would become a transition, exporting that nest out by itself, to them import it into AE 23.6 using Rosetta so I could use Twitch. I would then pre-render these to import them back into PrPro to have my transition. 

Between Roto & Twitch, I spent a good 10 hours editing VFX today. (I absolutely love what I do. That probably helps). Finally towards the end of the process, I threw an adjustment layer onto the timeline of PrPro and began correcting & grading using S_ColorFuse & Lumetri Color. Almost an hour into it, I finished and spent about 10 minutes on a S_Vignette. When everything was just about ready, I set my work area and began rendering the timeline.

 

The memory leak would occur at different times ranging between 15%-25% rendered. I'd like to restate that I keep up with space maintenance regularly and empty the disk cashe for AE at the end of every session. PrPro was the ploy applyication since the moment I finished using Twitch. I worked all day today, and for the past 5-8 months, without having any Memory Leak issue. The problem occurs today for the first time in months and I truly believe there is something about it that is related to Lumetri Color. It only ever happens when Lumetri Color is involved. 

 

My runner up guess would be Warp Stabilizer. But I don't have as much experience with this happening. I've used Warp Stabilizer often without Lumetri Color the last year. 


It's been a long time since I've have this issue, so I hope this helps. Be well ✌️

 

 

Side note. Not having the ability to use Twitch because AE 24 no longer supports Rosetta has me looking into alternatives for softwares. I've been with adobe since I first started editing and Twitch is the key to everything I do with my own personal aesthetic & style. I've never been one to leave for crashes. But if the future Adobe Products don't allow me to use Twitch, I'll find another way before I find another computer or effect. 

Translate
Participant
Sep 15, 2023 5:33 PM UTC

I'm having the exact same issue. What version did you downgrade to in order to resolve this?

Translate
Participating Frequently
Sep 8, 2023 2:57 PM UTC

Agreed.  Switch to Resolve.

Translate
Participant
Sep 8, 2023 2:20 PM UTC

There will be no news. I've been following this since May when I had the issue with a 2 minute video with a few transitions. Spent 2 days trying to fix it and talk to their support. They just ask you to upgrade, downgrade, check XYZ, and other guesses until you give up.

 

Do yourself a favor and switch to DaVinici Resolve. 

Translate
Participating Frequently
Sep 7, 2023 8:19 AM UTC

Any news?

Translate
Fergus H
Community Manager
Community Manager
Aug 29, 2023 4:29 PM UTC

Thanks to everyone who has responded and provided us with a way to reproduce the problem. We're looking into it and will update this thread when we have more information. 

 

Thanks,

Fergus

Translate
mickpeninsulaTV
Known Participant
Aug 29, 2023 4:21 PM UTC

I'm using 23.2 and I'm finding it the most stable, but it's not perfect, I still get mem leaks at least once a week if my project is open for more than 8 hours.

Translate
Participating Frequently
Aug 21, 2023 2:13 PM UTC

Hi,

I am running Premiere Pro version 23.6 on a Mac Mini M1 running Ventura 13.5.1 and am running out of memory, especially while rendering but soetimes while editing. What gives?  I thought this issue would have been resolved by now?  

Translate
Bruce Bullis
Legend
Aug 21, 2023 2:20 PM UTC

The issue has frequently been reported, but no steps to follow which actually reproduce the issue have ever been provided, or discovered.

We believe it's happening, and want to fix the problem; first, we need to reproduce the problem.

What step-by-step instructions can you follow, to reliably reproduce the behavior you're seeing? 

Do you see it with every sequence? every project? every type of input media? every output preset? [private upload space available upon request; DM me]

'especially while rendering' is interesting: Do you have a sequence with constituent media which, when rendered, produces the out of memory problem 100% of the time? If so, we'd also like an output preset (.epr file) containing the settings you're using.

Translate