Known Participant

Answered

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

Forum|Forum|3 years ago
March 15, 2023
118 replies
23156 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?

Show previous replies

A

alanog

Participating Frequently

Files uploaded.

A

alanog

Participating Frequently

Just testing with AME 23.4... and so far I'm seeing the same memory leak.

I'm starting to wonder if it's an OS update. This wasn't happening the other week (probably before I allowed the OS to update to 13.5.1 - though it's been on 13.x for a while now and not had any problems with PP (though not this specific project)

Bruce Bullis

Community Manager

Sounds great, Alan!

Link to private upload space sent.

What will enable us to jump on this = Step-by-step instructions on how to reliably reproduce the problem; steps [above] are very enticing. 🙂

A

alanog

Participating Frequently

I've got a project that exhibits this problem - was on 23.6 (AME) and now downgraded to 23.5 - same problem... physical memory chewed up and then it starts on the swap so my primary drive slowly ends up with no space left. I'll try downgrade to 23.4 next and see if that exhibits.

The footage was supposed to be a quick thing I was pulling together to demonstrate a mixing problem to a production team, so it's not got many edits in it. Happy to provide the project and the files.

AME - 23.6 / 23.5

PremPro - 23.6

OS: macOS 13.5.1 - M2 Mac Mini (Physical memory 16GB)

Using Metal on the encode for hardware - H.264 and tried with HEVC.

Always sending media from PremPro to AME. I'm not exporting directly from PP.

Video Source formats: Either a 720p @ 50fps 4.9mbps MP4 with AVC High@L3.2 / 128kbps stereo 48kHz AAC-LC or 1080p @ 30FPS 4mbps MP4 with AVC High@L4 / 128kbps stereo 48kHz ACC-LC - both sources which are from the same broadcast seem to result in similar memory leak problems. In one example the former video (the one at 50fps) has a single edit to trim the front, and a simple fade from black on the video and a fade in on the audio applied.

Steps:
1. Open PP. Created a new Project (in PP23.6). Dropped the two source files into my import bucket. Then created a separate sequence from each.

2. Trimmed each video in the respective sequences. Applied basic effect on Video (dip to black) and Audio (crossfade) to 'fade in' to each video.

3. Exported one sequence to AME. Fixed the settings to HEVC and matched the sequence settings, adjusted the video bitrate to variable single pass 2mbps, Metal used. Hardware encoding set as default (didn't touch that). Corrected the location of the output file (I always have to do that - it's frustratingly always stuck in an old folder... it *never* goes into the folder of the project).

4. Started the queue in AME.

Expected Result: an output from AME for an encoding video and my system should remain stable.

Actual Result: Memory used for AME became 46.34GB eventually, and free space on primary storage (MacHD) was used up. System became unstable. AME had stopped about 90% of the way through encoding the first sequence. 'Force Quit Applications' OS dialog appeared - "Your system has run out of application memory" - where it showed Adobe Media Encoder 2023 was using 46.34GB. My primary storage partition is only 128GB and it's claiming there's only about 12GB left. When I force quit AME, it will (and does) release the free space... which is why I think it's a swap / temp file.

I'm happy to provide my files (project, sources, etc) - but I'm not uploading them here.

Fergus H

Community Manager

Hi Len,

Thanks for responding quickly and I'm so sorry you had such a poor experience when calling support! That sounds really rough and a frustrating waste of your time. I will send you a DM and we'll go from there.

Regards,

Fergus

L

leonardd47297138

Participant

Hi,

I was ready to screen share the problem with your support team when the leak we had a few months ago crashed our entire documentary project. I was told to “call Apple” instead, and after a 2 hour screen share call with one of their techs - proving it wasn’t an OS issue - I called Adobe back, where I was told the only solution was to start a new project.

2 days and a painfully long, crash-strewn series of copy and paste procedures later, we got up and running again … though our new project file is still dangerously close to over running its RAM parameters again.

If you want to see the problem for yourself, I still have the original broken project (quarantined), and would be happy to demonstrate it to you.

Len

Fergus H

Community Manager

Hi all,

I'm a product manager in the video team at Adobe and one of my areas of focus is performance. We are very eager to get to the bottom of the issue that has been described in this thread. However, so far, no one posting has been able to provide us with steps to reproduce the issue and without that, it's very difficult for us to understand the cause of the issue, let alone fix it.

The information we need is described in this post about how to write a bug report: https://community.adobe.com/t5/premiere-pro-bugs/how-do-i-write-a-bug-report/idi-p/13361863

Related, it's very useful for us to be able to get media and project files that display the issue; no project is too large for us to handle. Additionally, we're happy to schedule a video call if there's someone in this thread who is willing to walk us through what they are seeing.

Regards,

Fergus

L

leonardd47297138

Participant

Wish this were so, but it’s not true. Memory leak happened to us, with no change in Premiere Pro version at any time.

Adobe have a nasty habit of sharing speculation, and typically, blaming someone else (eg Apple) for their software’s issues, usually in an effort to steer your complaint away from them.

Based on our experience, and those of others we’ve spoken to, the “only happens when you update the version during a project” line is false. Though, that said, it’s never good to let Adobe auto update, or change versions mid-project, and all applicable settings should be changed to keep it from happening.