Copy link to clipboard
Copied
I have an iMac 3.4GH 16GB of ram. I don't understand why I should suddenly be getting this message. I am using Mavericks 10.9. I use after effects CC the latest version.
The After Effects CC (12.2) update fixes this.
Let us know how it works for you after you've installed the update.
Copy link to clipboard
Copied
The bug mentioned by the original poster in AE version 12 was fixed.
The RAM leak bug in version 13.0 was also fixed.
You guys are sharing evidence of a different bug with similar symptoms. Read my suggestions in this thread: Re: "unable to allocate memory after effects CC 2015" Mac Pro bug fix?
Copy link to clipboard
Copied
jizz please fix it as soon as possible @A@
Copy link to clipboard
Copied
I'm starting a project that relies on Trapcode Form and this bug is stoping me cold. Please please address this.
Copy link to clipboard
Copied
brendanT wrote:
I'm starting a project that relies on Trapcode Form and this bug is stoping me cold. Please please address this.
Brendan, can you use CC 2014 for your project? That way, until the bug gets fixed, at least you won't be stopped.
If you left the Creative Cloud software at its default to remove your old versions when you updated to CC 2015, you can reinstall AE CC 2014 very easily: How to Find and Install Previous Version of Adobe Apps in CC 2015
Copy link to clipboard
Copied
About to try reinstalling CC14 - truly hope you're right in that this error only affects CC15. Getting this same problem when using Reg Giant Effects plugins - ToonIt in particular.
Copy link to clipboard
Copied
Thanks Szalam,
I couln't get creative cloud to reinstall 2014 but I was able to find a direct download link. This wasted several hours though. Feeling pretty burned by Adobe right about now.
Copy link to clipboard
Copied
Trying to rely on Creative Cloud app to keep files in sync and apps up-to-date is downright unreliable. Sometimes it's fine, other times I'm just stuck at "Installing 0%...". Of all the cloud apps I use - OneDrive, Dropbox - I loathe CC app the most.
Copy link to clipboard
Copied
I've just started getting this error and it happens CONSTANTLY. OS X.9.5 using AE CC 2015. I also get another error "unable to allocate enough memory to render the current frame" occasionally when rendering certain compositions.
Copy link to clipboard
Copied
It seems to still be occurring in its latest update. Working with some pretty heavy renders but also have 32g of ram and it shows that there's plenty left there and still get the message and eventual crash.
Copy link to clipboard
Copied
I uninstalled AE 2015 and reinstalled 2014 and everything is working perfectly fine now... took me hours to figure this out. I'll just work with the 2014 version until all of the bugs are fixed.
Copy link to clipboard
Copied
I've been getting this error for awhile now. I'm on a Late 2013 Mac with 64GB of RAM, two AMD FirePro D700 graphics cards, and a 500GB Flash drive for cache purposes. This error happens a lot when I use the Primatte Keyer, and I can't render long compositions (10 minutes plus) without the render engine crashing (I have to restart the software and pick up the rendering where it crashed).
I need the functionality of CC 2015, so I can't revert to 2014. Please fix this!!!
Jerry MacKay
Littleflick Pictures
Copy link to clipboard
Copied
Had this issue on AE CC 2014 (was eventually fixed) and 2015 (still happening) on my iMac 2013 - i7 3.5Ghz / 24GB / GTX780 4GB / Fusion drive running Maverick and Yosemite (up to date).
I worked for several Production Studios over the past 2 years and they also encountered this problem at one point or another.
I would be interested to know if anyone in the Windows verse encountered this issue? Because all the discussions and threads I read, everyone is on Mac.
It's getting frustrating to randomly loose work. And it's not even heavy duty stuff, just animating a simple mask on ProRes HD footage make it happen (and i've got nothing else running).
So if it is not something that plague the Windows version, i'm seriously thinking of switching back to the dark side.
FrankT.
Copy link to clipboard
Copied
Hi there,
This problem came back with the new update
I'm working on an animation with imported multipass from c4d.
I'm working with 16mb Adobe sRGB - linear color space.
It was pretty heavy but even when I work with proxys with lower res mp4 it happens the same.
Any suggestions?
Thanks in advance.
Joao Monteiro
----
www.joaomonteiro.tv
Copy link to clipboard
Copied
p.s - Sorry can't edit my previous post. I have the latest update installed (13.5.1.48)
Copy link to clipboard
Copied
mondi studio wrote:
p.s - Sorry can't edit my previous post. I have the latest update installed (13.5.1.48)
Try it with the latest update that came out last night: 13.6
Copy link to clipboard
Copied
Latest update and still the same error....
It's pretty sad that this has been going on for years without a fix.
Copy link to clipboard
Copied
Update since my last post in November!
Fist off, I've been plagued by this memory issue since updating to CC 2015 on my Mac. I would get random memory error while working on my comps. I notified Adobe and they said that the latest update would fix it. Well it did not, I think it actually made things worst now because it's saying that "AE cannot allocate 0.0010 MB of Ram" or 0.002 MB, and even 0.000 MB of Ram now; at which point I would have to Force Quit the App because the message would cascade indefinitely.
More recently, during renders, the memory usage would go up to 100% before crashing and giving the same message. I assume that this new behavior is do to the length of the comp I'm working on; used to be about 10sec per comp, but now I am working on comps that are more then 1 min long.
Some time I'm working in AE without a fuss, and other time I literally cannot get any work done at all. The error can occur once a day or so, not so bad. But sometime it popping up every 2 min!
I also did some experimentation to find the cause of this issue, or at least some hint has to what is going on:
-My primary workstation is an iMac 27" late 2013 i7-3.5Ghz, 24GB Ram, 4GB GTX780m, OSX 10.10; and my backup workstation is a custom PC from 2009; i7-940 2.93Ghz, 12 GB Ram, 3GB GTX660, Win 7 OS.
-Both computer use the latest Adobe CC 2015, have the same plugins installed, all plugins on both sides are on the same version.
-This week I've been working on a 3min long keying comp (pre-edited sequence rendered out has 1 clip in 1080p ProRes422 - 29.97fps). I was in a rush to get the sequence done asap and half way through the project the memory issue started popping up every 2 minutes or so. I tried purging memory in AE, still happened. Tried purging memory in OS, still happened. I managed to complete the chroma key by working "offline" with "Caps Lock" enable and switching live preview render on and off. Really not an ideal solution but it did the trick.
-Started to render out my comp and that where the memory would start to build up to 100% and crash the App. Not even a quarter of the way thru the render. I was fed-up so I consolidated the project and switched to my PC. Started AE, setup the render to .mov with Animation codec since no ProRes in PC, hit render and 5h later the job was done with an average of 25% out of 12GB ram used! This is insane! I then tried to render to .mov with Animation on my iMac, memory still happen.
-Even tried to play with the Secret menu option, no change.
I usually work with heavy 3D comp inside AE with Element 3D and I can understand that at some point AE can't take it anymore since it's sort of a "hack" of the App that normally can't handle true 3D. But this time it was just a simple chroma key job. I only used three simple 3rd party plugins; Neat video's "Reduce Noise v4" and RedGiant's "Matte Feather Sharp" and "Light Wrap". I used "KeyLight+KeyCleaner+AdvSpillSupp" presets for keyer.
I have to say that I did found a work around that will probably not work for every one. I was desperate to get this issue out of the way so I started scrubbing thru some old Time-Machine backup, found 1 from late 2014 with AE CC 2014 installed. I simply copied the AE sub-folder from the backup Application folder to my computer main Application folder, updated the plugins for AE CC 2014.... and voila!!! I was able to open my AE CC 2015 project in AE CC 2014, make some changes to it and render it without any memory issue!
My 2 cents in all this, I think Adobe really dropped the ball on this one. After Effects CC 2015 for Mac is the least stable App Adobe came up with ever, and I've been working in the Adobe verse since 2001 (AE v5). Is it solely Adobe's fault, maybe not. Apple probably bare part of the blame for making new OS every year for the past 3-4 years which can be hard to keep up with on the "dev" side. I can image they're spending more time on maintenance then actual development. But denying the existence of such a clear and pretty bad issue serve no one. Stop arguing and get to work Adobe!... Please.
Copy link to clipboard
Copied
Not Apple's fault. I have exactly this problem on Windows 10. Same solution as well. Works fine in CC2014. So far Adobe support have been defensive and dismissive. They insist I don't have enough ram (I have 8gb) but AE only uses 2.1 (out of an available 6.4) for the particular project that's causing the error message.
Copy link to clipboard
Copied
I´m also having this problem now... Havn´t had it before but since i updated to the latest version of AE CC 2015 it started to come up frequently! Version 13.6.1. Annoying as hell! I also updated to El Capitan so maybe it could be that to?
Copy link to clipboard
Copied
I am having the same problem
Copy link to clipboard
Copied
TripleNipple wrote:
I´m also having this problem now... Havn´t had it before but since i updated to the latest version of AE CC 2015 it started to come up frequently! Version 13.6.1. Annoying as hell! I also updated to El Capitan so maybe it could be that to?
That seems really irritating!
Have you tried updating to 13.7?
You could try rolling back your OS too, but that shouldn't be a problem. Other than AE not playing previews back in realtime unless you hide the timeline (longer explanation here), AE version 13.7 should work on El Capitan. A lot of folks using El Capitan aren't experiencing this issue, so there's got to be something specific that's triggering the problem. Does this happen for you in every project? For example, if you just have a shape layer moving across an HD composition (using one of AE's presets), does the issue still happen? If not, let's dive into the contents of the compositions that are causing the error as well as the specific hardware of these machines.
Copy link to clipboard
Copied
I'm on AE 13.7 with OS X 10.9.5 and having the issue constantly. It happens with I'm switching out of AE into Premiere Pro (Not dynamically linking). When I switch back, I get the "unable to allocate memory" message. Also, I get the "Cached preview needs 2 frames or more frames for playback". Any idea when Adobe will actually fix this issue, or do we just wait for another new splash screen on start up?
Copy link to clipboard
Copied
james.vandeusen wrote:
I'm on AE 13.7 with OS X 10.9.5 and having the issue constantly. It happens with I'm switching out of AE into Premiere Pro (Not dynamically linking). When I switch back, I get the "unable to allocate memory" message. Also, I get the "Cached preview needs 2 frames or more frames for playback".
I seem to recall hearing someone else mention something like this, but it was a while ago. Specific information like what you have would probably be quite helpful to Adobe as they try to narrow down what is causing the error. I'd recommend filing a bug report: Feature Request/Bug Report Form The more info they have, the sooner it is likely to be fixed.
Copy link to clipboard
Copied
So, I have found that removing Trapcode on our system has fixed the issue. I'm not sure who has Trapcode here, but we are on Trapcode version 12.1.9. There are updates to Trapcode that might fix the issue, but it seems to be where the memory leak is. Hope that helps anyone else having the same issue.
Copy link to clipboard
Copied
I'm having the same problem. This is pretty ridiculous. It doesn't happen right away, which makes me think there's a memory leak of some sort. Also, it's the first time I'm using a LUT file. Never had this problem prior to that.
I'm on AE 13.7
Mac OSX 10.10.5
This seems to be an ongoing problem. Never had this problem with CC2014.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now