Activity › Forums › Adobe Premiere Pro › Anybody else running out of memory with CC2015?
-
Anybody else running out of memory with CC2015?
Rick Steele replied 9 years, 5 months ago 16 Members · 22 Replies
-
Jaap h. Boerhof
December 1, 2015 at 10:26 amToday there is a new version of Premiere Pro CC available: CC 2015.1
This update It has quite a list of improvements as can be seen here:
https://helpx.adobe.com/premiere-pro/kb/9-1-bug-fixes.html
We know this update fixes a memory leak when using 3rd party video transitions and several other effects. -
Brian Cooney
December 1, 2015 at 7:56 pmthis just started happening to me this past week.. I installed the latest Adobe updates today so maybe that will fix it. I did notice (I’m running Yosemite) that i didn’t have NVIDIA Web Driver selected but OSX default graphics driver.. must have changed it by accident in the desktop menu dropdown… wondering if that had something to do with it.
Telly Award Winning Editor and Motion Gfx Artist with MotionFoundry, Inc., Nashville, TN. Former Head of Post Production, Coca-Cola Studios Atlanta, GA.
-
Trent Happel
December 1, 2015 at 11:08 pmIf possible, could everyone try the CC 2105.1 (9.1) update? There were fixes in 9.1 related to effects memory leaks.
Trent Happel
Adobe
Premiere Pro -
Lionel Johnson
December 14, 2015 at 6:54 pmI had the same problem, I’ve been to an apple store and they told me to uninstall the adobe cloud and reinstall it.. I did it and it used to work well for 2months but now the problem is back I don’t know what to do!
System
Late 2013 MacBookPro
2 GHz Intel Core i7
8 GB 1600 MHz DDR3 -
Aj Koch
December 18, 2015 at 9:47 amThis exact issue popped up immediately AFTER I upgraded to 2015.1. No problems with the prior version of 2015.
I’m not using Lumetri scopes. I am working in a rather large project, and it takes a few hours of work before I see the error. I’m using native .mxf files, but working in a timeline configured for ProRes422. Editing 23.976 footage in a 29.97 DF timeline.
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
64 GB 1866 MHz DDR3 ECC
AMD FirePro D700 6144 MBI have allocated 48 GBs to Adobe products in preferences, leaving 16 GBs for the rest of my processes. Have tried setting rendering optimized to both “Performance” and “Memory” with the same errors.
Submitted a bug fix form. Please do what you can to fix this leak. Thanks!
-
Gary Hegenbart
December 23, 2015 at 5:23 pmI was having issues with Premiere Pro and Media Encoder. I updated both apps and it seems to have resolved the issue. My PP version is now 9.1.0 (174) build. I exported a 30 min project from Premiere with Activity Monitor open and the highest RAM usage I saw was just under 7GB.
I use a MacBook Pro (2013) with 16GB.
-
Veronica White
December 28, 2015 at 10:01 amI ran out of ram 1 min and 20 seconds into a project. Added another 4Gb of ram and it still won’t let me complete the project.
-
Ryan Poduska
April 29, 2016 at 8:22 pmAJ, I just spent a couple of days on tech support (and numerous technicians) with Adobe concerning this same issue I was having. It turns out that the cause of the problem is the Intel Iris graphics card. Even though Adobe has it listed on their supported system requirements, they said that you need a bigger graphics card to render your project that has ANY effects placed on it. So the two options you have is to either bypass the graphics card or upgrade the graphics card to a supported NVIDIA card. To bypass the graphics card for rendering, go to File > Project Settings > General and change the “Video Rendering and Playback” to “Mercury Playback Engine SOFTWARE ONLY” setting. This bypasses the graphics card and everything renders just fine regardless of what effects are used in the project.
-
Brian Cooney
April 29, 2016 at 10:08 pmMan.. I did something last month that I thought I’d never do. I bought a PC after using mac since 2001. I actually love it. PPro is rock solid on it. It feels like FCP7 used to on the Mac. After all the issues I’ve had with my Macs and Adobe over the last 2 years. I’m finally glad I made the switch.
Telly Award Winning Editor and Motion Gfx Artist with MotionFoundry, Inc., Nashville, TN. Former Head of Post Production, Coca-Cola Studios Atlanta, GA.
-
David Notowitz
June 15, 2016 at 7:29 pmI’m having these exact same problems with my MacBook Pro (Retina, mid 2012), and it’s several versions later of Premiere. (I’m still running OS 10.10.5, and I have 16GB of memory and an Nvidia GeForce GT 650M and 1024 MB).
Anyone have a permanent solution for this? If I upgraded to the newest OS would that solve the issue?
Thank you!
All the best,
DavidNCAVF, The National Center for Audio and Video Forensics
https://www.NCAVF.com
Reply to this Discussion! Login or Sign Up