Skip to main content
RapidKing
Participant
November 1, 2014
Answered

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

  • November 1, 2014
  • 23 replies
  • 90361 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.

23 replies

dcp1957
Known Participant
October 28, 2015

Having issues while rendering out on 9.0.2.

2013 Mac Pro with 64GB of RAM and it still isn't happy! It is blowing through the cap!

alaing44808599
Participant
September 15, 2015

We are also seeing this same problem when trying to export clips from Premiere Pro CC 2015. We've tried the fix mentioned but the problem still persists. Yes we've updated PP to the latest version 9.0.2. We're on an older Mac Pro 3,1, 32GB of RAM, graphics card is an NVidia GeForce 8800 GT with 512MB, OS X 10.10.5. Please find the memory leak. We want to be able to run the latest version of PP without having to rollback to the 2014 version.

Participant
September 16, 2015

We now have the same problem on all our machines since the latest update this week of Premiere CC 2015 and Media Encoder.

Very frustrating if you are running 5 edit suites and none can export or transcode files anymore... because of a memory leak...

We are woking on Mac Pros with 16GB RAM on each machine.

Is there a way of downgrading to the previous version ?

Inspiring
September 16, 2015

I believe you can re-install the 2014 version - the same as  I have done with my PC.

I'll not be touching anything connected with the 2015 version until these forums go relatively quiet on it.. I'm quite happy with 2014 performing more or less as it should.

Participating Frequently
August 15, 2015

I have the same problem,

Done everything possible and now installing older version of premier , i might be lucky.

I oure professional work, this is not acceptable,

I have Faith in Adobe to fix that issue ASAP

keithmholland
Participating Frequently
August 3, 2015

I am running a 2015 macbook pro with the new Graphics card and I just got the message from the force quit menu. It seems to only be happening with the scopes open but I am color correcting so that's not really a good option. Quitting and reopening seems to be the only thing that clears the memory. Good thing I got that SSD.

2015 Macbook pro - NVDIDIA 2gb

Panasonic GH4 4k in multicam (6 streams, 1 stream 1080)

Kevin-Monahan
Community Manager
Community Manager
August 3, 2015

Hi Keith,

I am running a 2015 macbook pro with the new Graphics card and I just got the message from the force quit menu. It seems to only be happening with the scopes open but I am color correcting so that's not really a good option. Quitting and reopening seems to be the only thing that clears the memory. Good thing I got that SSD.

2015 Macbook pro - NVDIDIA 2gb

Did you install the Premiere Pro CC 2015 (9.0.1) update released on Monday yet?

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
keithmholland
Participating Frequently
August 4, 2015

I hadn't realized there was a new version yet. Updating right now. I'll let you know if it fixes the issue

Inspiring
July 21, 2015

Been through a big hoop on this one.

Now back on PP 2014 and project running smoothly. I did increase memory to 32GB which improved overall performance a little but nothing to jump up and down about.

However - the last 10 attempts to render have resulted in a number of oddities;

  1. System runs out of memory
  2. CPU usage goes to 100% and sits there until I close the out of memory message
  3. Renders fail with the low memory message (with or without Mercury)
  4. Successful renders are flawed in that content from multiple tracks goes missing presenting black screen where it should have been.

Getting concerned about losing customers if this goes on too much longer.

PC

win 7 pro

SSD OS disc

4 x spiny 500 in a Raid

NVIDIA GTX690

Participant
July 20, 2015

Ive just come across this problem.

Had a CC2015 project working fine on a early 2011 MBP.

Just bought a brand new 15" MBP Retina, 16gb Ram, 2.5ghz Processor and today that exact project is constantly getting out of memory errors causing me to do 3 restarts this morning already.

Have reverted back to CC2014 and spent past hour rejigging the project from an XML export.

CC2015 desperately needs a bug fix update!

Odd it suddenly occurred with newer model MBP.

Kevin-Monahan
Community Manager
Community Manager
July 20, 2015

Hello Conan,

Ive just come across this problem.

Had a CC2015 project working fine on a early 2011 MBP.

Just bought a brand new 15" MBP Retina, 16gb Ram, 2.5ghz Processor and today that exact project is constantly getting out of memory errors causing me to do 3 restarts this morning already.

What were you doing as you got the out of memory errors? Was the Color workspace open? Were you exporting?

Thanks,

Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Participant
July 21, 2015

Hi

Just editing varying codecs in a sequence. Mix of MP4, MXF and H264. No colour workspaces open.

The fix suggested in a previous thread of moving the preferences folder and disabling sync settings worked for me so id think this is the problem.

Participant
July 13, 2015

I don't know if any of you have already seen this temporary fix to the "out of memory" problem, but my issues have been fixed (Premiere Pro CC 2015 on a 15" Macbook Retina -- 16GB RAM) by going to the preferences > Sync Settings and unchecking all the boxes.

I was getting the "Out of Memory window" every 20 minutes and having to restart, but since I unchecked the sync settings, it hasn't happened again.  I hope it gets permanently resolved soon, because that caused a lot of delays in my work over the past two weeks!!  Really frustrating!

Kevin-Monahan
Community Manager
Community Manager
July 13, 2015

I don't know if any of you have already seen this temporary fix to the "out of memory" problem, but my issues have been fixed (Premiere Pro CC 2015 on a 15" Macbook Retina -- 16GB RAM) by going to the preferences > Sync Settings and unchecking all the boxes.

I was getting the "Out of Memory window" every 20 minutes and having to restart, but since I unchecked the sync settings, it hasn't happened again.  I hope it gets permanently resolved soon, because that caused a lot of delays in my work over the past two weeks!!  Really frustrating!

Thanks for reporting back on this issue.

Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
James@doorbellmedia.com
Inspiring
July 6, 2015

Closing Lumetri scopes, and updating my CUDA driver in system preferences seems to have helped. Be sure to reboot after each step. Can't really say if it was one or the other or both but things seem to be running smoothly again. However, in my activity monitor it still shows Premiere eating up a ton of ram, about the same as when I was getting the out of memory error message. Will continue to report back with any significant findings.

Kevin-Monahan
Community Manager
Community Manager
July 13, 2015

Closing Lumetri scopes, and updating my CUDA driver in system preferences seems to have helped. Be sure to reboot after each step. Can't really say if it was one or the other or both but things seem to be running smoothly again. However, in my activity monitor it still shows Premiere eating up a ton of ram, about the same as when I was getting the out of memory error message. Will continue to report back with any significant findings.

Great news! Thanks for letting us know.

Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Participant
July 14, 2015

hey Kevin'

i tried all of the above solutions but nothing is working..

will there be an official update in the near future or will we have to use the workarounds?

The problem appeared out of nowhere and was not directly connected to the update from cc 2014 to cc 2015, so it has to be something within premiere pro that has suddently caused the memory glitch..

thanks

Inspiring
July 2, 2015

Same issue here on PC / Win 7 pro / SP1 / 16GB RAM / Nvidia GTX90 dual SLI - BUT ONLY since upgrading to PP CC 2015, it never happened in PP CC 2014

I get a few minutes editing done and then this;

I have checked with the makers site and I am running the latest drivers.

This to me looks like an issue brought about by PP CC 2015 and looks like I'm being forced to buy more memory - possibly even change my GPU.

I too am suffering latency and performance issues so badly I went and bought a replacement keyboard and mouse set - only to find it hasn't improved anything.

This machine is purely for editing and minor graphics manipulation so it doesn't have MS office, email or anything on it.

While editing I rarely have any other programmes open, least ways from now on it's not really an option I can afford - so everything else gets shut off.

Not too happy at the moment.

Kevin-Monahan
Community Manager
Community Manager
July 2, 2015

Hi Scuba Badger,

Same issue here on PC / Win 7 pro / SP1 / 16GB RAM / Nvidia GTX90 dual SLI - BUT ONLY since upgrading to PP CC 2015, it never happened in PP CC 2014

Sorry this happened to you. The focus of this thread is memory leaks in OS X versions of Premiere Pro CC 2014 and Premiere Pro CC 2015. Since you have a Windows machine and different behavior, you should create a new thread with all your details. I found this doc from NVIDIA, but the fix is related to updating drivers and you said you already did that. Therefore, I would like to focus in your GPU memory issue specifically, so I look forward to assisting you on that new thread.

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Inspiring
July 2, 2015

Thanks Kevin

I've taken this to a PC Users thread...: Premiere Pro causes your system to run out of memory (PC Users)

Dave

Dinu T
Participant
July 2, 2015

Same thing here, on a late 2013 Yosemite (I had this error running CC 2015 on Maveriks too which led me to the Yosemite update) 3,5 ghz i7 iMac with 32 GB of ram, NVIDIA GTX 780M 4096 MB. I am editing a 30 minute long comp shot in 3 cameras and after only 10 - 15 minutes of editing I get the "System has run out of application memory" error. I tried changing the Mercury Playback Engine to both OpenCL and CUDA - still got the error. I could not try to edit while on Software Only because with some filters on it was too slow for my needs, and I couldn't meet my deadline. While I got the error, the Activity Monitor showed Premiere Pro CC 2015 using about 29 GB of my Physical memory, with huge swap files - over 60 GB, and in some other cases it showed Premiere Pro CC 2015 using about 17 GB, the rest (up to 32 GB) being used by the kernel_task. I don't run anything else other than Premiere Pro when I am editing and my system drive (that holds the swap, cache, etc) has over 550 GB free space. Besides having this error, I feel the system is a lot less responsive than it was a couple of months ago (although nothing else changed, besides the CC and OSX update) - when I play the 1080p sequence I am working on (simple cuts, with a Warp Stabilizer and a color correction filter on some of the clips) the moment the play head reaches a cut the image in the program view window starts to drop frames, and it even freezes sometimes. This is very annoying as not such a long time ago Premiere Pro was running quite smoothly on this system, working on similar sequences with similar amounts of data involved. What could be responsible for this memory leak issue - a Premiere Pro bug, an OS bug, both? Thank you for your time.

Kevin-Monahan
Community Manager
Community Manager
July 2, 2015

Hi there Dinu,

Same thing here, on a late 2013 Yosemite (I had this error running CC 2015 on Maveriks too which led me to the Yosemite update) 3,5 ghz i7 iMac with 32 GB of ram, NVIDIA GTX 780M 4096 MB. I am editing a 30 minute long comp shot in 3 cameras and after only 10 - 15 minutes of editing I get the "System has run out of application memory" error. I tried changing the Mercury Playback Engine to both OpenCL and CUDA - still got the error. I could not try to edit while on Software Only because with some filters on it was too slow for my needs, and I couldn't meet my deadline. While I got the error, the Activity Monitor showed Premiere Pro CC 2015 using about 29 GB of my Physical memory, with huge swap files - over 60 GB, and in some other cases it showed Premiere Pro CC 2015 using about 17 GB, the rest (up to 32 GB) being used by the kernel_task. I don't run anything else other than Premiere Pro when I am editing and my system drive (that holds the swap, cache, etc) has over 550 GB free space. Besides having this error, I feel the system is a lot less responsive than it was a couple of months ago (although nothing else changed, besides the CC and OSX update) - when I play the 1080p sequence I am working on (simple cuts, with a Warp Stabilizer and a color correction filter on some of the clips) the moment the play head reaches a cut the image in the program view window starts to drop frames, and it even freezes sometimes. This is very annoying as not such a long time ago Premiere Pro was running quite smoothly on this system, working on similar sequences with similar amounts of data involved. What could be responsible for this memory leak issue - a Premiere Pro bug, an OS bug, both? Thank you for your time.

I understand and apologize for the bad behavior. Please check out my post for potential workarounds.

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Dinu T
Participant
July 3, 2015

Hey Kevin,


Thank you for your fast answer. I wanted to chime in to confirm that in my case the memory leak was related to the "Sync settings" - turned Syncing off, followed Rob's advice from the link you shared and everything seems to be running fine now - memory usage is back to normal, no more errors and Premiere does run better.

Appreciate the support!

Have a great day