Skip to main content
Known Participant
March 15, 2023
Answered

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

  • March 15, 2023
  • 118 replies
  • 22911 views

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 has been closed for replies.
Correct answer Bruce Bullis

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?

118 replies

Participating Frequently
April 8, 2024

Hi Mitch

This all makes perfect sense. Of course there's always a history, this production kind of grew larger than anyone thought at the start and should have had a more stringent workflow. From my history ( way too much of it ) I have always worked on the basis of splitting productions up on any NLE/DAW platform ... just to spread the risk. I like to work in 10 minute blocks... each one a seperate Project ( or Library or whatever the high level container is called ) .  But I have noticed that many (most ?) users dont think that way though, and the word "Project" just leads to the current situation when 'everything' gets put inot one project.  And to be honest I'd wager 80% of work done in NLE's are short form, so this doesn't crop up much!

Since I could open our project on an Intel Mac I have been able to remove all the audio effects ( all Premiere, no third party) which weren't really needed at this point in the production anyway.  Save it for mixing !  I was wondering about how Premiere dealt with the plugins ... useful to know they all get loaded for the whole project.  The Project is now a third of it's size, and I'll let you know if we have success opning it back in the Editor's Apple Silicon environment.

 

Thanks for the Production documentation too. I will pour over it. Never seen it before.

 

And thanks for the support ... we really appreciate it!

Remote Index
Inspiring
April 8, 2024

Mitch W,

 

Thanks for your post on this issue.

 

You say: “Your project size is getting overly large (currently 115MB). … The best thing you can currently do to avoid the problem is to … decrease project size”

 

While it is not surprising to learn that Premiere Pro has limits on project size, it’s frustrating as a user to have to guess about limits and discover by trial and error. Why would any user think "this project might be overly large" if there is no guidance anywhere on what constitutes reasonable sizes?

 

Why does “project size” return no hits in your documentation?


If Adobe expects users to manage project size (again - not an unreasonable expectation on its own) then guidance on this issue would be helpful. Why not be helpful? Why make users guess?

 

R.

 

@Kevin-Monahan(documentation issues)

@Mitch W 

Mitch W
Community Manager
Community Manager
April 8, 2024

Hi Lee,
I don't know if everyone in this forum thread is suffering from the same issue that you are, but there are two primary components to your particular memory consumption issue.
1.) Your project size is getting overly large (currently 115MB). It's not an unmanagemable size yet, but it's rapidly approaching it. Your project contains  286 sequences, 3990 project items, and 102064 track items. All these items require memory to load. Your best avenue for managing the large project size is to break this single large project into multiple smaller projects within a Premiere Pro production. In a production, individual projects are treated like bins. 1 project might contain just the media for scene 1, another project might contain just the media for scene 2. A third project might contain just the sequences for scene 1, etc.. A production uses hidden cross project referencing so that the media for the sequences in one project might live in another completely different and seperate project. Because only the currently open projects in a production consume memory, the result is that the overall memory usage is reduced. You can find out more about productions here: 

https://helpx.adobe.com/premiere-pro/using/long-form-episodic-best-practices.html. There are also lots of YouTube videos available on using productions if that is preferred.

2.) You project contains a lot of audio effects. We instansiate all of the audio effects used in your project on launch. Because you have a lot of sequences (286 sequences) in your project all using a lot of audio effects, we eat up a lot of memory. We (Adobe) need to do a better job of using memory to load these audio effects. We could definitely do better here. We now have a backlog item filed against this ineffcient behavior and will get it reviewed by product management and our developers. But... addressing this problem is likely to take some time and isn't going to be simple. The best thing you can currently do to avoid the problem is to use Premiere Pro productions to decrease project size and decrease the currently required memory usage.
Thanks again for helping us by providing the files. We very much appreciate it.

Cheers,

Mitch

Community Manager
April 5, 2024

@Lee36533728tdqc  Ok, thanks, that looks fine.

Mitch W
Community Manager
Community Manager
April 5, 2024

Hi Lee,

Yes, I got the process sample.Thanks! If you can also send me your project file, it would help in getting this addressed.
Thanks again,

Mitch

Participating Frequently
April 7, 2024
HI Mitch

I uploaded an archive of two recent ‘saves’ of the project files to the same download link I sent you before.

Thanks for your help!

Lee
Participating Frequently
April 5, 2024

Hi Mitch

 

I PM'd you the info you wanted. Could you let me know if you got it?  The messaging app kind of freaked when I hit send, and I don't know if anything got transmitted! 

Participating Frequently
April 5, 2024

Sure...

This is the current default config. to the Mac Internal SSD ( 450 GB free ) But we tried all combinations of other Thuderbolt 3 drives with at least 6 TB free to no effect. 

Of course we detled All the Cache files too..

Mitch W
Community Manager
Community Manager
April 4, 2024

Hi Lee,
If you upgraded from 23.x to 24.x, your 23.x project still exists unless you manually deleted it. When PPro 24.x opens a project made in an earlier version, it makes a copy and all future changes are then made only in the new project. I suspect you can probably still find your project file from 23.x.

Some additional troubleshooting steps here would be to navigate to Macintosh HD/Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/ Select any files and folders you find there and drag them to your desktop. Make sure this folder is empty, then restart Premiere Pro. If your memory issue goes away, then the problem was related to some 3rd party plugin that was installed. You can then start putting those files/folders back to the MediaCore folder 1 at a time, then relauching Premiere Pro to see if you can identify the culprit.


If removing all the 3rd party plugins doesn't fix the issue, try capturing a sample process that we can have a developer look at. While PPro is in the hung/frozen state, open Activity Monitor and capture a sample process for Premiere Pro. To do this, select the Adobe Premiere Pro 2024 under the Process Name column then click on the System diagnotic options button at the top (meatball button) and choose Sample Process. When the sample is complete, click the Save button. If you PM me, I'll let you know where to send it and we'll see if we can identify what's eating up all the memory.

Community Manager
April 4, 2024

@Lee36533728tdqc Could you post a screen shot of your Preferences>Media Cache... so we can see how it is set up? 

Bruce Bullis
Community Manager
Community Manager
April 4, 2024

We don't have any specific guidance; we still haven't been able to repro the behavior. [And yes, we've been trying.]

I would start by looking for backups of your .prproj files, from before the upgrade.