Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Anybody else running out of memory with CC2015?

  • Anybody else running out of memory with CC2015?

    Posted by Blaise Douros on June 29, 2015 at 7:58 pm

    Hey all,
    I am having an issue that is new to me in CC2015; periodically, I run out of application memory, and I get this dialog box (with the exception that Premiere is red, and has the word “Paused” next to it):

    System:
    Late 2013 iMac
    3.4 GHz Core i5
    32 GB RAM
    NVIDIA GeForce GTX 775M, 2 Gb
    Yosemite 10.10.3
    Second monitor connected via Thunderbolt. No other peripherals except hard drives and headphones.

    This has been happening no matter what media I use (I have a mix of AVCHD h.264 and XAVC media, but it happens even on sequences that are exclusively one kind of media, without discrimination). As you can see, I’m not running a ton of apps in the background, and never had the problem before CC2015.

    EDIT: It seems to happen to me more often when I scrub around a lot in the timeline.

    Please, no trolling about how this is what I get for supporting the CC business model or whatever.

    Anyone else seeing this, have a solution, or perhaps Kevin Monahan can chime in?

    Rick Steele replied 9 years, 5 months ago 16 Members · 22 Replies
  • 22 Replies
  • Tom Metcalfe

    June 29, 2015 at 10:10 pm

    Yes, I am having this issue too. The new 2015 is using all of my 16 gigs of memory with a very simple project.

  • Vicky Ryder

    June 29, 2015 at 10:56 pm

    Yes, I encountered this last night while in the new Lumetri panel. Haven’t tried much else in PPRo 2015. I am on an iMac 5k with 32 GB! And I’m told it’s not a legit memory error. I will be digging in more later tonight but wanted to “second the motion” on your error. I believe it is a bug but will come back with what I find out.

  • Vicky Ryder

    June 29, 2015 at 11:35 pm

    And yes, it happened to me when I started making changes via Lumetri panel while clip was playing / I was scrubbing. Didn’t have the issue when working on a particular frame.

  • Blaise Douros

    June 30, 2015 at 12:30 am

    Yes, this is the bit that is getting me. On simple projects, it takes a lot longer to happen, but on complex projects, I am having to restart Premiere every hour or so. Maybe a memory leak of some kind.

    Or maybe it’s PP’s way of telling me to get off my butt for a couple minutes and stretch my legs 🙂

    Glad to know that I’m not the only one. Not glad, obviously, that others are experiencing the issue, since it’s a bugger!

  • Blaise Douros

    June 30, 2015 at 4:23 pm

    Kevin Monahan has confirmed over in the Adobe forums that this is a memory leak caused by the Lumetri Scopes. It seems that closing this panel should allow us to work smoothly until it’s color correction time.

    They are working on a fix. In the meantime, we can file bug reports here.

  • Vicky Ryder

    June 30, 2015 at 5:28 pm

    Thanks. Lumetri is one issue. People are reporting memory leaks with other processes and plugins. For the record, I hadn’t tried much else besides Lumetri, but I do hope my problem is limited to that known issue. I will do more testing later and file a bug report. (And reply to that thread.)

  • Blaise Douros

    June 30, 2015 at 6:06 pm

    Yeah, even without Lumetri running, it’s still happening for me, but it takes longer. I’ll be filing one, as well.

  • Frankie Os

    October 10, 2015 at 11:27 am

    I am having the same issue on 2 different imacs with similar yet different OS:

    Imac 27 inch (late 2011)
    12 GB on Yosemite
    Mostly used for rendering in the background

    Imac 27 5k (late 2014)
    12 GB on El Capitan
    Editing / rendering etc etc

    I am mostly working on multi screen audio visual installations. This means that I am working on strange timeline formats such as 3X1920 in width X 1080 in height for composition. usually those files would be split to 3 X 1080 p. This workflow has been working for years and been conducted without any single preview or export problem up until CC 2015.
    This was an extremely well maintained system with PPro + Adobe media Encoder and OSX.
    Files that i have exported many many times before suddenly pose a huge problem. I get errors about memory on both, PPro and media Encoder:

    At a crash the activity monitor shows this:

    My current solution is: split the files that I export into chunks, set the preferences of PPro to “optimize for memory” and export from Premiere Pro one by one.

    Needless to say that this is killing my workflow. Both computers were blocked for 3 days just finding ANY feasable solution. The source of this problem however remains unclear. No lumetri used here!

    HELP!?

  • Jeremy Nivison

    November 10, 2015 at 12:19 am

    Any updates on this? I’m having the same issue when exporting a short video with ultra key and a few other effects.

  • Timothy Geraghty

    November 18, 2015 at 4:09 pm

    Any updates on this? Having the same trouble myself, whenever I’m trying to export or work in more than two of the Adobe CC programs at once or when I try to export a layered premiere sequence using AME i get the following message. (Notice activity monitor).

    Simple sequences work ok sometimes. I may also try and break into chunks and export but this will kill my workflow for sure. I’m fine if it takes 10 hours to render as long as I can count on it to work.

    I’ve contacted abobe and they said to move third-party plugins out of pref’s but still having trouble.

    TIM

    Model Name: Mac Pro
    Model Identifier: MacPro6,1
    Processor Name: 8-Core Intel Xeon E5
    Processor Speed: 3 GHz
    Number of Processors: 1
    Total Number of Cores: 8
    L2 Cache (per Core): 256 KB
    L3 Cache: 25 MB
    Memory: 64 GB
    Boot ROM Version: MP61.0116.B16
    SMC Version (system): 2.20f18
    Illumination Version: 1.4a6

Page 1 of 3

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy