Skip to main content
E
Ed25665058m7l0
Participant
October 10, 2022
Question

Run out of application Memory 2022 M1 Max

  • October 10, 2022
  • 4 replies
  • 5786 views

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 

    This topic has been closed for replies.

    4 replies

    F
    Felix284463599exg
    Known Participant
    October 23, 2023

    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
      VisionEars
      Participating Frequently
      November 15, 2024

      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?

       

      S
      SPIIKIIZI
      Participant
      July 12, 2023

      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. 👍

      D
      Dino221833121r8g
      Participant
      July 13, 2023

      try turning off Auto Transcribe, auto detect language

       

        D
        David M. SoundsWrite
        Participant
        December 27, 2022

        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.


          Kevin-Monahan
          Community Manager
          Kevin-MonahanCommunity Manager
          Community Manager
          October 12, 2022

          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

          Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
          E
          Ed25665058m7l0Author
          Participant
          October 13, 2022

          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
            Community Manager
            Kevin-MonahanCommunity Manager
            Community Manager
            October 14, 2022

            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

            Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
            Terms & ConditionsAccessibility statement
            Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices