• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
3

my Premiere 2024 takes up all the memory of the MacBook

Community Beginner ,
Jan 20, 2024 Jan 20, 2024

Copy link to clipboard

Copied

I’m working on a MacBook M2Pro 16 memory, I updated Premier 2024 to the latest version and all the memory started disappearing. Tell me what to do, I can’t workСнимок экрана 2024-01-20 в 13.07.29.png

TOPICS
Error or problem , Hardware or GPU , Performance

Views

704

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jan 22, 2024 Jan 22, 2024

Copy link to clipboard

Copied

Hi @Nikolas33508345nhwv,

Thanks for writing in. That looks alarming. Can you try creating a new project and then importing the older project into the new one as a test? Perhaps you have a corrupt project file. That can happen if updating mid-project. Let us know if that helps.

 

Thanks,
Kevin

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 24, 2024 Jan 24, 2024

Copy link to clipboard

Copied

I'm having the same issue with Premiere 2024 with a specific project. It causes premiere to use around 120 gb of memory although my total is 64. Premiere is clearly overriding the memory usage settings. It's causing my mac to crash. Before the crashes, my system is slowed down because it is clearly using memory swapping with the HD to get that 120 Gb.  It is apparenly premiere that is corrupting project files as I've never seen this in previous version. To add to that, Adobe deleted Premiere 2023, which is spcifically set it not to do. I have a very fast Mac Studio. So none of this should be happening. This is a bad show all around. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jan 24, 2024 Jan 24, 2024

Copy link to clipboard

Copied

Hi @Divergence Studios,

Thanks for the message. Have you tried what I recommended for @Nikolas33508345nhwv? I hope that might work for you. Let us know. Sorry for the issue.

 

Thanks,
Kevin

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 24, 2024 Jan 24, 2024

Copy link to clipboard

Copied

Yes I did. I created a new project and imported all the items from the other project. Then I set up two outputs into the queue for ME. The memory used by Pr stayed under 4GB. The memory usage of ME grew continuously until it crashed at 110.71 Gb. The first of the two outputs did not complete. This was my 4th attempt to output a 20 minute video. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 24, 2024 Jan 24, 2024

Copy link to clipboard

Copied

Then later, I tried again by exporting straight from Premiere (with ME not running). I was able to successfully export a 4k version of a 20 min video. The memory usage of Premiere 2024 grew to 78 Gb. I then attempted to output an HD version of the same video and Premiere crashed at the point, using 111 GB.

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 24, 2024 Jan 24, 2024

Copy link to clipboard

Copied

Then I made a 27 second preview of the previously mentioned file. When I exported that via Media Encoder, the usage of Pr and Me was 133.6 Gb and 6 GB respectively. I don't normally have Activity Monitor running. So I don't know what is normal. But this seems excessive. And Adobe apps crashing and taking all application memory is obviously not normal and needs to be corrected asap. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 25, 2024 Jan 25, 2024

Copy link to clipboard

Copied

I just re-installed Pr 2023 and opened a different project as Adobe will not allow a version of Pr to open a project created with a later version. Is there a reason for this or does Adobe do it to make things more difficult for its customers? 

 

I setup a batch export of two videos 17 & 20 min respectively. At about 80% complete, Pr 2023 is using 1.26 GB and ME  2023 is using about 5.2 GB. The total would be over 100 Gb at this point with 2024 versions. At this point Adobe owes me at least six months credit on the subscription for all the time I've wasted on this, not to mention all the work I will have to redo.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jan 29, 2024 Jan 29, 2024

Copy link to clipboard

Copied

Sorry to hear that troubleshooting is not working for you, @Divergence Studios. What are the specs of the footage you are working with? Is it 10-bit 4:2:2 4K H.264 media? Let us know. 

 

Thanks,
Kevin

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 31, 2024 Jan 31, 2024

Copy link to clipboard

Copied

Hi Kevin,

 

Here is info provided by the Media Info app: MPEG-4 (QuickTime): 2.19 GiB, 5 min 19 s
1 Video stream: HEVC
1 Audio stream: AAC LC

Overall bit rate mode: Variable
Overall bit rate: 58.9 Mb/s
Frame rate: 43.688 FPS
Encoded date: 2023-12-10 16:40:14 UTC

I believe it was shot on an iPhone. Is the variable bit rate a problem? I know in the past that Premiere didn't do well with VBR. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jan 31, 2024 Jan 31, 2024

Copy link to clipboard

Copied

Hey @robertk47971964,

It's not variable bit rate that's the issue, it's the variable frame rate (VFR). That's a pretty odd VFR frame rate. It could be the cause of issues. Try transcoding it in Media Encoder. If that won't work, try Shutter Encoder. Is it working better now? Let us know.

 

Thanks,

Kevin

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Feb 08, 2024 Feb 08, 2024

Copy link to clipboard

Copied

Yes, I meant frame rate. I ran the other files from the project through HandBrake to convert to constant frame rate. Ithen edited and output with no problem. 

 

Now that we are in 2024, it's about time that Adobe products be able to handle variable frame rate. Many people shoot on mobile devices and don't know about such settings. I should have caught it during edit. But Adobe should be able to deal with it. The simple editing software that comes on an iphone can.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Feb 10, 2024 Feb 10, 2024

Copy link to clipboard

Copied

Hi @Divergence Studios,

Thanks for the message. VFR handling is supported. My observation is that it seems there is a limit to how far support for VFR can go without breaking. I see that you had a clip with a frame rate of 43.688 frames per second. What were your sequence settings? Where they widly different?

 

I do know what you mean, though. I've been working with a lot of this footage lately and have found that transcoding VFR footage on ingest to ProRes LT gives the best results as I work and for export, especially of other effects, like Lumetri Color and Warp Stabilizer needed to be added.

 

Feel free to let the team know how you feel with a feature request, here.

 

Thanks,

Kevin

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Feb 13, 2024 Feb 13, 2024

Copy link to clipboard

Copied

It is such a weird frame rate. I allowed the project to set itself up based on the video. In the future, I will run vfr clips through handbrake first. I didn't notice this time beforehand. Hopefully I won't experience any other big problems with 2024 premiere or ME. Thanks.

 

Bob

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Mar 03, 2024 Mar 03, 2024

Copy link to clipboard

Copied

thanks for your reply! But you won’t believe it, I deleted Adobe Creative through which I updated Prime and the problem disappeared. I've been working without creative cloud for two months now.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Feb 13, 2024 Feb 13, 2024

Copy link to clipboard

Copied

This is definitely a thing, and I don’t remember running into it before. The screen shot below is for a relatively simple project, tutorial videos. So the 1080p sequences are almost completely cuts-only edits on a single video track with no effects, and the media format is 100% screen captures created using native macOS screen recording. Each sequence is about half an hour long, in Premiere Pro 24.2.0. (It was also happening before the last update.)

 

Premiere-Pro-memory-usage-excessive.jpg

 

With that memory usage in mind, note that my Mac (M1 Pro MacBook Pro, macOS 13.6.4) has 32GB of unified memory, and rarely complains about memory usage in Adobe photo and video apps. It is alarming to see these Adobe applications requesting many times more memory than is physically installed in the Mac. But I don’t necessarily panic about that, because I understand that the reason macOS doesn’t reach that error state until memory usage is well beyond 100GB is because of the way macOS can use RAM compression and swap files to juggle the balls in the air as long as it can. The concern is that these apps managed to push macOS over the cliff, which I rarely see. This Mac is usually rock solid for weeks with Adobe apps.

 

There are only two features that are frequently used in these sequences. One is Essential Sound; I have applied Dialogue adjustments to all audio (it’s narration). I am using transcription to do text-based editing (very useful!); at one point I wondered if Premiere Pro was having trouble managing that new feature’s metadata or something because it was hard to think of other features in use that could cause such a problem.

 

Originally I had all sequences in one project, but because macOS was telling me that opening it made Premiere Pro want over 100GB of memory, exceeding even the ability of macOS to manage it, I broke it up so that each lesson uses one project with one sequence in it, and am now managing the job as a Production. But all that does is keep each individual project from overrunning macOS memory management, because each sequence can still use many tens of GB when opened.

 

At one point I tried exporting a project to XML and opening that back in Premiere Pro, in case there was corruption, but that didn’t help; the new version exhibited similar memory usage.

 

The Adobe Media Encoder memory usage is so high because I watched it add roughly 10GB of memory use for every 3 to 5 minute in-out segment of a sequence that I add. Now I stop adding to the queue when AME exceeds 100GB memory usage, render those, quit AME, and then restart it just so I can add more sequences to render.

 

Also — Premiere Pro and AME are not releasing memory when projects/sequences are closed or deleted. If AME racks up over 100GB memory usage and is finished rendering, the only way to free up that memory is to quit AME…because deleting all already rendered sequences from the queue doesn’t reduce memory usage at all.

 

I don’t know if this will help, but I have seen similar memory complaints in threads about other Adobe applications, for example in the Lightroom Classic community: Lightroom Classic memory usage spirals out of control, into the hundreds of GB, until macOS throws its hands up and cannot go on. I only mention this in case the Premiere Pro engineers need to confer with the Lightroom Classic engineers, like if it’s actually a bug in OS memory management. That link is just one example, there are numerous similar Lightroom Classic customer threads that you can easily find with a web search. 

 

The unpredictability is also similar, in that for both Premiere Pro and Lightroom Classic, it isn’t happening to everyone. It isn’t even consistent for me. Although I have obviously seen this problem in Premiere Pro, I spend even more time in Lightroom Classic and have never seen it misbehave with memory like some are describing.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Mar 03, 2024 Mar 03, 2024

Copy link to clipboard

Copied

thanks for your reply! But you won’t believe it, I deleted Adobe Creative through which I updated Prime and the problem disappeared. I've been working without creative cloud for two months now.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 26, 2024 Mar 26, 2024

Copy link to clipboard

Copied

LATEST

Hi Nikolas, has this continued to work for you? using Premiere without Cloud?
Im definitely experiencing the same thing.  Premiere is currently using 30gb as it idles, without a project even open.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines