-
Premiere Pro CC2015.3 and .4 Memory leak
Hi,
Has anyone upgraded to Premiere Pro cc2015.3 and .4?
I upgraded about a week or 2 ago, and have since noticed a severe memory leak on all my projects.
Basically I open the project (in some cases with approx. 50-100 clips of .MTS files. When I open the project, the RAM spikes up to about 4gb to start, and then holds there once all items are loaded. Once I start scrubbing the timeline, or playing the timeline, it spikes up to about 8-9gb of RAM used. From there, it dips a bit, but continues to climb until within 10 minutes or so, I’m maxing out at about 13 gb of RAM used. My system then freezes pretty much, and I have to restart. It’s been awful. I’ve talked to tech support twice now, and we’ve tried everything, but so far still the same problem. Has anyone seen this, and have you come up with any resolutions? I’ve also noticed the same RAM spikes when using both AME, and After Effects. All problems started with the update to 2015.3.System – Dell M4600, windows pro 7, Intel Core i7 Dual CPU’s at 2.80ghz, 16gb RAM, Nvidia Quadro K2100M
Thanks for any insight,
Mike
-
2 Replies
-
I haven’t noticed a memory leak on OS X, but I don’t have any Windows machines to compare at this time. I’d assume a memory leak would be isolated to the windows version.
I notice a lot of rendering problems, and generating peak files, conforming, etc…is taking a rediculously long time. Premature upgrade based on Adobe’s track record the last two versions, but I actually NEEDED the proxy on/off toggle and figured that feature might outweigh the bugs. So far, it’s been incredibly mysterious. Eat machine has it’s own bugs with PP 2015.3.
-
Interesting update,
so the projects I’ve been editing have been with original camera footage that is .MTS It seems for some reason when loading RAM takes a spike (this part makes sense), but when even just moving the playhead in the timeline the RAM spikes. So the MTS files are fairly large causing very large spikes in RAM. I then edited a bunch of clips that were H264 mp4s. Much smaller files, smaller spikes in RAM.
A workaround would be to use proxy’s, but it’s a lot of extra time, work, and storage to create proxys for 200 clips every time I have a big project.Mike
Reply to this Discussion! Login or Sign Up