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

[ItsJustRich]

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?

[Avihai30495170zgcz]

same issue here on my Mac Studio m1 MAX 32gb ram.

even when i downgraded to previous versions the issue remains.

it seems like the ram limit you set on premiere pro settings isn't working anymore.

[defaultdfslh5hg0wxb]

I been having the same issue! With the 23.3 and 23.4 less frequently, but it still happens sometimes. That's a mayor bug and you need to solve it!

[Avihai30495170zgcz]

i found the solution.

all you should do is to open adobe creative cloud and next to premiere click the 3 dots and then click on open(intel).

[alphabetikal]

still happening to me, m1 Studio Ultra 64GB, Prem 23.4 

Footage Red 6k and Go Pro 360. No issues when proxies are on, its when doing the online/finishing

[gregorygheorghiu]

I've been having this issue too. I just updated to Premiere version 23.5, running Ventura 13.2.1 on an M1 Pro Macbook Pro with 16gb ram.  I've tried everything everyone has mentioned in this post, other than just reverting back to a much older version of Premiere. Nothing's worked.

I haven't even created a sequence yet! I'm just importing footage into a new project, and I've been getting the application memory error about every 10-15 minutes. It's infuriating. This also happened a lot on my last project, which was a BTS package for a pretty big multi-editor network gig. It cost us a ton of time (particularly our poor assistants who spent day after day trying to figure it out). Just chiming in to hopefully help alert Adobe that this is a serious problem.

I've seen it recommended elsewhere that switching to the Intel version of Premiere might help. I can't tell if that's a facetious suggestion ... has anyone tried it? Or does it seem worth trying?

[defaultdfslh5hg0wxb]

A few days ago I wrote that with the versions 23.3 and 23.4 I wasn't having this issue, but with the version 23.5 I did. I think, at least for me, the issue appears when exporting, in any case I use a Lumetri mask and the final video is more than 15 minutes long, because I've been exporting videos with the same mask but shorter (10 minutes long) and everything went smooth. Please Adobe, stop making me waste my time and missing my deadlines and already solve this major problem!

[brandonbaker.tv]

Just upgraded to v 23.5 and I am still having this issue. 2021 M1 Max 32gb Ram.

Most of my commercial work is only a few h.264 files less than 5 minutes long.

DaVinci Resolve is sounding real tempting right now. Has there been any real solutions given by Adobe? 

[ItsJustRich]

Nope, 3 or 4 versions in people still having the issue, amongst about 50 others, make a complaint to customer service, these forums aren’t always checked by adobe staff.

[Layla30674757fnau]

The only fix I could find for this problem was to install an older version of the software. It now runs the same tasks that were  chewing up memory and causing crashes without any issues. Looks like a bug in recent versions of Premiere.

[ItsJustRich]

I managed to capture the log file during this happening if adobe want it? or where to post it?

[Bruce Bullis]

Sure! [reached out directly]

[robbiem42595415]

Same issue for me. Had to downgrade to 23.2 to fix a different bug, but 23.2 has the memory leak issue. It's so disruptive.

[Bruce Bullis]

In what version did you see the behavior, before moving back to versions < 23.2?

[robbiem42595415]

The memory leak issue was there in 23.5 but not as pernicious/common. In 23.2 it appears after an hour of having the project open. 

23.5 had a bug that meant my program window was black when source clip LUTs were enabled. I've had 2 different remote help sessions, both advised to downgrade to 23.2, but it's not workable.

[robbiem42595415]

I have 12 days of documentary footage and over 50 sequences, so recreating the project is not an option.

Can we just have at least one stable version of Premiere please?

Apple M1 Max

32 GB

13.4.1 (c)

[David31364008ersf]

I've been having the same issue. 

M2 Pro 

16 GB RAM

Happens in both Premire Pro and Media Encoder. Extremely frusturating, tried everything imaginable, spent hours on the phone with Adobe. 

A little work around is I noticed my compyter gets to around 30% of the video before force quitting so I'm going to try and export it in thirds and then reassemble in iMovie. 

[Bruce Bullis]

Anything remarkable/interesting in your sequence, about 30% of the way through its duration?

[David31364008ersf]

Nope. All of the transutions/effects are in the intro. The issue appears to center around Premire compatabity with new macs as opposed to specific export settings or stuff like that.

[kgbeats]

Also having this issue! Premiere version 23.5 running Ventura 13.2.1 on an M1 Pro Macbook Pro with 16gb ram. Long project (1h20m), warp stabilizer on all clips. Happens 3 different times after short editing sessions, none of my stuff was saving. Crashed when opening media encoder as well. Finally, got to export after seval attempts of giving up and losing progress, had to render an unfinished product..

[Bruce Bullis]

Thanks for the further info.

>The issue appears to center around Premire compatabity with new macs...

There's something more to it; it's not that simple.

We develop and test on a broad assortment of M1 and M2 macs, with various MacOS X versions, and have not been able to reproduce the problem.

[David31364008ersf]

It might not affect all Mac users, but the common denominator in this specific thread is that all members reporting issues are using newer Silicon Macs. I can't even call it an "issue" since it makes the entire software useless. Other threads with memory leak issues center around different adobe software. I tried doing a full reset of premire pro and media encoder (using the .old extension and then restarting my computer), along with reinstalling different versions of the software. The issue persists! Could there be something I'm missing?

[Bruce Bullis]

> Could there be something I'm missing?

We're all missing something; specifically, step-by-step instructions which allow us to reliably reproduce the issue.  

Yes, the problem seems to only occur on M1 or M2 macs, but >99% of PPro users using those chipsets don't encounter any such problem. Frustrating, for all involved.

[mickpeninsulaTV]

[robbiem42595415]

From my time with support over the phone, they are well aware of the Apple silicon memory leak bug. An Adobe support supervisor told me that the issue may be linked to projects created in one version and then continued in another version after an update/downgrade. There is currently no clear fix for this for existing projects that suffer from this bug, so they had to close my case even though it was unresolved.

The 'minority' reporting the memory leak bug reflects editors who have either changed version mid-project or have inherited projects from a collaborator from a different version. You probably won't get any complaints from post houses as they will most likely be working on very old versions.

My advice to everyone creating newer projects is to stick to one version of Premiere Pro and disable auto-update, supposedly this helps. I can't confirm as all of my projects are legacy projects and have gone through 2-3 versions.

After my expierence I've been trying DaVinci Resolve 18 where my projects run much smoother. I'm currently testing it to see if I can re-create my workflow there and migrate once I can convince production house clients to switch. M1 has been out for years now so these kind of bugs are unacceptable and a sign that users should begin looking elsewhere.

[David31364008ersf]

I ended up switching to Final Cut Pro. Have been happy as a clam ever since.