Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects AE rendering error (memory leak?)

  • Kevin Camp

    June 19, 2009 at 6:08 pm

    in the render queue, near the top left corner, i noticed your ram hit 92%…. it should never get higher than 60%, which is about the highest you should ever set the maximum ram cache setting in the memory & cache preference or risk stability issues….

    so, what are your current memory & cache settings?

    i’d really recommend the defaults… max memory usage: 120%; max ram cache: 60%. if you run into problems, then you might lower the max ram cache setting. the general rule for the disk cache is only enable it if you have an external media drive for renders and media, and, when enabled, the disk cache should be on the system (boot) drive. this is to prevent a data bottleneck on a single drive bus and get degraded performance.

    Kevin Camp
    Senior Designer
    KCPQ, KMYQ & KRCW

  • Bret Snyder

    June 19, 2009 at 10:03 pm

    120% and 40%, with disk cache unchecked. I turned it down from 60% when I did the latest tests, including the one from the screenshot.

  • Bret Snyder

    June 22, 2009 at 9:36 pm

    I now have 12 gigs of ram installed and when it renders out, it still shows a % of 3 gigs being used in the render queue. Shouldn’t that number be much higher?

  • Bret Snyder

    June 22, 2009 at 9:54 pm

    Weird thing happened. The memory cap remained at 60% for the first probably 15 minutes of the render process, which I assume is correct behavior…then out of the blue, it started raising beyond the cap of 60% and by the time it was at 87%, it gave me the Keylight has run out of memory error message. I was running with 5 cores turned on.

    It’s gotta be a bug with Keylight or AE, yeah?

  • Kevin Camp

    June 23, 2009 at 2:41 pm

    3gb is the most ram that can be allocated to a 32-bit foreground process (ae is only 32-bit), so 3gb is right on.

    i’m not sure, but i think the issue may be with keylight already being multi-threaded and ae’s method of multiprocessing… even with mp off in ae, keylight will use multiple cores since it’s code is multi-threaded. that may be causing an issue with ae’s multiprocessing method.

    i have encountered some comps that i have needed to disable mp to render (although not with keylight, and i do a fair amount of keying), bu that may be the case here.

    you might also see if you can send this issue to the foundry’s support, they may have a better work around than disabling mp in ae…

    you could also post on adobe’s ae forum, just to see if anybody over there has seen this issue…

    Kevin Camp
    Senior Designer
    KCPQ, KMYQ & KRCW

  • Nout Mans

    September 13, 2009 at 7:47 pm

    Why isn’t the secret turned on by default….?
    it seems to work just fine!
    i see the precentage of ”ramm used” run up to 25% and then it jumps back to 9% after the clearing of the ramm…

    what’s wrong with that?
    Why isn’t this standard, does it make the rendering slower or something?

  • Peter Monty

    November 30, 2012 at 2:19 am

    This worked. Go to edit and select Preferences then Memory and Multiprocessing. Up the 0.5GB to 1GB or more depending on how much RAM you have. if on 4GB of RAM then go up to 1GB. Your error notification will now be gone and shots will render. Also check a tick into the ‘Render multiple frames simultaneously’ Box.

Page 2 of 2

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