Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Memory problems still a big issue in After Effects 22

Contributor ,
Nov 14, 2021 Nov 14, 2021

I thought it would be somehow improved, but it doesn't:
The memory management of After Effects.
Even though I set it to "let other programs use 12GB", here you can see how much of my 64GB were used only by After Effects right before I closed it (because it gave me, once again, a memory error. It couldn't finish the render of a proxy clip, because that process, again, didn't care about available memory at all), on a freshly booted machine:

Ninarama_0-1636905617866.png

And here are my memory settings:

Ninarama_1-1636905844339.png

I was lucky this time, because usually AE crashes with a blue screen (imagine: on Win10 !!) and the computer reboots.

...but it actually doesn't matter at all what numbers you choose in the settings. It always gets ignored after some  minutes doing anything where frames get cached in After effects. In this case, the warp stabilizer was involved which is also known for eating up something like 2GB per second, and also not caring about the memory settings, whyever that is.
It maybe that AE itself honors the memory settings, but some components of it seems to act like they don't care: The render process, the warp stabilizer, etc. they just grab more and more memory no matter what.
You can also notice this, when AE "flatlines" in the memory-graph of the task-manager although you render new frames, that's a clear sign that it reached a limit and tries to stay inside this limit.
But any time you start warp stabilizer, render something, etc. you can clearly watch this limit to be ignored and the usage going up again until it reaches almost the upper ceiling and cause all kinds of memory-related errors then.

I think this is an absolute joke. Also because this is an ongoing problem for over 10 years now.
Premiere does not have all these problems. Maybe because it's been aquired from another company back then which didn't employ that mysterious and completely insane programmer that once introduced this mess to the codebase.

 

One thing to alleviate that would be to have a "no-cache-at-all" setting!
If the GPU is strong enough, not every single frame has to be put in RAM. It would be great to have the option to turn the constan caching of everything just off. Or at least a "don't use 200% of you RAM for cache only" or "only cache max. x number frames". I could rather live with a sometimes lower FPS than those constant crashes.

TOPICS
Error or problem
71
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
no replies

Have something to add?

Join the conversation