Participant

Answered

Premier Pro runs system out of application memory (CC 2014 & CC 2015 on OS X)

Forum|Forum|11 years ago
November 1, 2014
23 replies
90556 views

As I edited about a 20 minute clip of video, the memory consumption of Premiere Pro CC 2014 on my MacBook Pro (Core i7, 16GB memory, 500GB SSD with 150GB free, Yosemite) grew and grew. Now, when I open the project, Premiere Pro immediate consumes 30GB of memory! Which means that opening my project now takes about 15 minutes (the blank Premiere application appears in about 2 minutes, but the panels do not complete their slow fill-in for another 13 minutes - all the while the cursor is spinning, not allowing me to select anything, and activity Monty tells me that Premiere is unresponsive). Worse still, when I try to export my project, memory usage grows above 60GB, until my system gives up and reports "Your System has run out of application memory". Keep in mind that I been careful to reboot the system, reset PRAM, and run nothing significant except Premiere, Activity Monitor and Finder. I have Optimized for Memory in preferences, and even tried Limiting Memory usage to 8GB (even though this refers to RAM, not VM).

I monitor Premiere steadily gobbling up resources as VM usage and Memory Pressure increase. I understand that the proximal cause of the error message is probably an excessive number of page faults triggered by the massive memory hogging by Premiere. However, the root cause is Premiere using so much memory.

My 1920x1080 project timeline and bin contain .MTS files (from AVCHD footage), .mpg files (converted via ffmpeg from .TOD files), One EPS graphic, Five .PNG graphics from PowerPoint, One Title, and less than 10 audio files extracted for editing in Audition.

When the export begins, Premiere estimates about 1 hour to encode my timeline. After about 35 minutes, Premier has used up over 60GB of VM which causes Yosemite to report an error, and pause the application.

One solution I suppose is to tell Premier to stop buffering so much content. I have a fast SSD with over 100GB remaining at the time of error, and I can live with the export taking an hour longer if some artifacts are left on disk.

Is there a way to tell Premiere to load less into Virtual Memory?

Message was edited by: Kevin Monahan

Reason: needed more descriptive title

This topic has been closed for replies.

Correct answer gepetto77

In File/Project Settings/Generel under "Video Rendering and Playback" switch the renderer from "Mercury Playback Engine GPU Acceleration (Open CL)" to "Software Only".

It will be a slower render but at least it should render. Works for me anyways.

Show previous replies

S

stevel76387034

Inspiring

Hi there,

I am now getting this error after updating to CC 2015. I did not previously have this problem. But now when I try to render sequences, after about 10 minutes I get the error that the system has run out of application memory. I'm then presented with two options- resume or force quit. When I resume, the computer freezes with the spinny rainbow pizza. When I force quit, Premiere closes, but the computer then becomes unresponsive and I have to force restart.

I'm running Macbook Pro from 2014, with 16 gb of ram. I have 11 dedicated to Premiere and 5 for other applications. Nothing else is running, and there are no clear memory leaks. I tried switching to software rendering as suggested, but I encountered the same problem.

Any ideas?

S

stevel76387034

Inspiring

Changing the Mercury Playback Engine setting to Software Only seems to have fixed it. So I assume this is an OpenCL problem?

D

DMcD Productions

Participating Frequently

I'm having the same memory leak problem. I'm on Premiere Pro 9.0.2 and was able to narrow it down to the Lighting Effect I used on my clips. Both suggestions here didn't work for me. I wasn't using the Lumetri scopes so that window was already closed. I moved the sync settings folder like described in this thread but I still had the memory leak which I was able to watch happen through iStat Menus. About 5 min into the render my RAM usage would steadily increase, even beyond the 11 GB cap which I set for Premiere all the way until I get the OSX error message that I ran out of application memory. I was able to export smaller segments of my timeline with the Lighting Effect and then reassemble them into one video. This was very annoying and time consuming since I had to restart Premiere every time to clear my RAM but I don't want to compromise the quality of my work for a client cause Adobe needs to address a bug issue they have yet to fix.

After this I did a test and removed the Lighting Effect and was able to export the timeline with no problems. I monitored my RAM usage with iStat Menus and it never peaked over 2 GB.

I noticed this thread has been inactive since August 3. I upgraded to Premiere Pro CC 2015 back on August 14 and have been running it with no problems, however I had not used this Lighting Effect until this weekend. I did install the 9.0.2 update on September 21. Kevin-Monahan do you know if this bug was fixed at one point and now has returned? Or is Adobe still working on an update for this??

The sequence I was exporting is about 8 min, mostly H.264 .MOV files off the camera and some dynamically linked AfterEffects clips with graphics and lower thirds.

iMac 27" Mid 2011

OSX Yosemite 10.10.5

3.4 GHz Intel Core i7

16 GB 1333 MHz DDR3

AMD Radeon HD 6970M 2048 MB

Further Bouknight.Jonathan post about Lighting Effect, I am in the same predicament. I have spent the last week reading all the tricks that various frustrated PP CC 2015 editors are desperately using to get their projects rendered and exported. I have done two clean installs of Yosemite and CC 2015. I have a variety of angry clients that do not want to hear about Adobe software problems. Since the memory leak has not been fixed by Adobe, I have to resort to re-installing PP CC 2014 and hope that I can finish my 20 little 5-minute edits. Major bummer especially since I thought I had flushed out all my frustration by switching from Final Cut Pro to Adobe. Happy Halloween. It would be nice if Adobe offered CC customers the real treat of software that actually functions.

Just finished my first 5-minute edit back in PP CC 2014 with all default project settings and all the audio and video effects I wanted which rendered in AVCHD 59.94 and exported H.264 YouTube HD 25 with no problem, way faster, and with this activity monitor

Very different from the PP CC 2015 yellow and red leaking to a crash.

G

gepetto77Correct answer

Inspiring

In File/Project Settings/Generel under "Video Rendering and Playback" switch the renderer from "Mercury Playback Engine GPU Acceleration (Open CL)" to "Software Only".

It will be a slower render but at least it should render. Works for me anyways.

ChrisTheWizard

Participant

sadly this didn't work for me...

GAH is there a way to save down to cc 2014 because this bug forces me to hard reset my computer each time...

JlkapnTax

Participant

Agreed. This Premiere eats too much memory and there is no way to stop it. I wish that there an option returned which allows setting a history limit for Premiere.

VisionEars

Participating Frequently

Same problem here on PP and M1, but granting full disk access to PP looks like it does this trick. Here is a link: https://community.adobe.com/t5/lightroom-classic-discussions/quick-tips-how-to-give-full-disk-access-to-lightroom-classic-on-macos/td-p/12913413?linkId=100000196562295&fbclid=IwAR2sGgjNm4A3eYsIPEvVeQ_BWSmoXugBW1nYvFiR8xsxAuvMPI3MeT0K7xs

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded