Run out of application Memory 2022 M1 Max

[Ed25665058m7l0]

Hey Everyone,

I've recently run into an issue with my M1 max 32g Mac Studio with Premiere. I often get an error saying "Your system has run out of application memory" and premiere pro is using up to 120g of memory sometimes.... which makes no sense becuase I only have 32g. Now my M1 laptop with on 16g is getting the same message. So it has to be premeire not the M1 chip right? I've seen a few articles referring to it as a 'memory leak' any advise is welcome. See screen shots attached. Side not, I've had the computer looked at by a professional and nothing is showing up as wrong or not working. 

Apple M1 Max, 32g Memory, MacOS Monterey 

[Kevin-Monahan]

Hi Ed,

It sounds like you have a corrupt sequence or project. Try creating a new sequence and copy/paste the clips there. If that doesn't work, make a new project and import the sequences you need from the previous project to the new one. I hope one of these solutions might help you.

Let me know.

Thanks,
Kevin

[Ed25665058m7l0]

Hey Kevin, 

Thanks so much for reaching out, I seem to get this error with every project I create. I create about 3 new projects a week. So do you think it would still be a corrupted sequence? 

My next option would be to downgrade my Mac OS Monterey back to Big Sur and see if I get the same issue. I've seen a few articles recomending this. 

[Kevin-Monahan]

Sounds pretty odd, Ed. I am sorry you are going through this. If you are creating new projects and have the same problem, perhaps not. Can you point me to any threads or articles which recommend downgrading macOS? I'd like to check those out.

Thanks,
Kevin

[Luciano Foglia]

[Abuse removed by moderator] Does not work. It does something for 30 min. Then back to the same. Same specs than the dude here and look at this massive memory leak. Tried downgraded a version and it's the same. I may downgrade to 2001 version maybe. That would be a lot better than this useless upgrades.  [Abuse removed by moderator] And get some work done to fix it!

[Keep your language civil or risk being banned from the forums]

[Luciano Foglia]

A yes that's Figma. at 93 MB ... the company that you are about to bomb. Another Macromedia case ... 

[Kevin-Monahan]

Hey Luciano,

Sorry for the frustration. Please file a bug with the devs here.

Yes, it is true. That is the advice I give for projects exhibiting memory leaks. It usually works OK for a quick fix. I don't believe it's useless advice if it helps most people keep working; it doesn't always solve everyone's issue entirely or permanently, however. I wish it would!

Memory leaks are often project-specific if the app does not have problems universally. For example, my projects on an ARM Mac don't exhibit the same behavior. No one on User Voice has yet reported a widespread problem with memory leaks and the current version...

The difference is the contents of your project file, the footage you are using, the effects you have applied, the workflow you are using, and so on. I observe that projects with memory leak issues are not simple. They are often copies of copies of projects. They have been updated across major versions. They contain a lot of media objects in the projects. In cases like this, you sometimes have to rebuild the project as it is too broken. 

You can benefit from rebuilding projects into a Production, which can operate a series of leaner project files and, thereby, avoid the tendency to spring memory leaks or other corruption. Consider it. Above all, project files can be pretty fragile when you move them across versions, as I mentioned earlier.

Since I do not know the history of your project or anything about what's going on with your media, etc., it is a bit more challenging to give specific advice. I would be happy to provide more detailed troubleshooting advice with more info. Let me know if you want further help. I can also get you assisted support if you prefer.

Thanks,
Kevin

[mickpeninsulaTV]

\I have the sane issue with every project now -M1 2022 mac pro

[David M. SoundsWrite]

I think all the talk about corrupt sequences is a distraction. This is a system wide issue that Apple needs to address with better communication. I know this is about AE and Adobe but perhaps my experience is relevant. 

I was getting the same message with Final Cut Pro on both a Macbook Pro M1 and an M1 Mini both with 1TB SSD and 16G RAM running both Monterrey and Ventura. I was suffering with constant beachballs during editing and then with then with this message when trying to export. 

The issue paritally resolved when

1) I unpacked all my compound clips so that there was less nesting in the timeline. 
2) I got rid of all system extensions relating to kernel usage that showed up in EtreCheck- can't remember all the exact terms but it mean deleting Google folders in the System Library. Deleting Logitech Options for my Marble mouse etc.

[SPIIKIIZI]

I have an M2 pro Mac mini and the same issue. It just collapses at the 95GB.

But the same project works on Macbook Pro i9 processor. (which shows me, that project takes 135gb to still work).

This is nonsense and frustrating. The whole day lost with NO solutions and even reinstalled Mac mini M2.

Mod note: profanity removed. Please abide by Adobe Community Guidelines. 👍

[Dino221833121r8g]

try turning off Auto Transcribe, auto detect language

[Felix284463599exg]

i am currently working on a windows system and ran intot he same problem since the update to 24.0 never had this notification that adobe is running on low system memory ever before. i got answers on other posts that my ram is to low to edit 4k footage wich simply isnt true because before 24.0 i was working with 4k footage and 16gb of ram and everything was working smooth and fine and now all of a sudden its my ram haha. i dont know what they did but i simply cant work properly. premiere using up to 99% of ram wich never happend ever before. my windows explorer.exe is crashing or something else on my system is crashing. Please Adobe, stop tellking us its our system when it clearly isnt.

[VisionEars]

Same issue here: Working with Mac M1 16Gb Ram.  Work for 20 mins, then "Your system has run out..."  How long has this been going on - years?  Why can't the brilliant code-slingers at Adobe get a fix on this?