ADOBE AFTER EFFECTS: Forum Expressions Tutorials Creative Cloud

ram leak

COW Forums : Adobe After Effects

<< PREVIOUS   •   FAQ   •   VIEW ALL   •   PRINT   •   NEXT >>
charlie hughesram leak
by on Jan 26, 2011 at 3:25:40 am

What's wrong with my system?

I have 12 gigs of RAM running windows 7 with a baddass graphics card and when i open my footage ( xdcam 422 at 24fps/ 23.98 ) into either premiere or after effects I can literally watch my RAM climb until it reaches 98% and crashes everything.

Just to clarify, I'm doing nothing but having the project files open with footage in them.

Before it starts eating the ram away, I can smoothly cut and edit footage for about five minutes no problem.

Return to posts index

Graham MacfarlaneRe: ram leak
by on Jan 26, 2011 at 10:09:56 am

Which CS version are you running?

Have you checked AE/Premiere memory settings to check that they allowing enough RAM for the rest of your system?
Also have you checked your task manager so see if all RAM really is being used by AE/premiere, or if there is any other suspicious RAM usage by other processes?

Graham Macfarlane
3D animator and VFX specialist
London UK

Return to posts index

charlie hughesRe: ram leak
by on Jan 26, 2011 at 3:06:52 pm

I'm running CS5 and watching the task manager shows a perfectly steady climb of ram for 4 or five minutes until all is taken and system crashes.

IN FACT: I've been editing in 3 minute periods with the task manager open, saving and quitting before RAM usage reaches 100%. After quitting, it drops right back down to nothing again and I re-open premiere and edit for 3 minutes again.

The graph of my usage is a flat horizon with a steep mountain the second I open up a comp with this footage.

Return to posts index

Kevin CampRe: ram leak
by on Jan 26, 2011 at 3:32:11 pm

what are your memory & multiprocessing settings in ae, and are you running any other software other than ae and the os when this happens?

Kevin Camp
Senior Designer

Return to posts index

Cory PetkovsekRe: ram leak
by on Jan 27, 2011 at 12:40:25 am

You need to divide and conquer. You have too many variables. Develop a test that eliminates half of them. Then another test that eliminates half of those until you have the offending cause.

Does it happen when you aren't using the system, just with the programs open?

What specific actions cause the memory to continually rise? You mentioned opening. How about editing/moving clips/layers around? How about previewing?

Is it caused by AE or Premiere? Leave only one open and see if it occurs, or if it requires the combination.

You say the system crashes, but it is highly unlikely the program is crashing windows. What specifically crashes and how does it crash? Does a window pop up saying premiere has stop working and it closes? Or does windows get a blue screen or what specifically?

You talk about a comp with some specific footage. Does the memory leak occur with other footage, or in the case of AE, no footage, just shapes, and solids and effects?

Narrow it down and be specific or you'll never solve it.


Cory Petkovsek
Corporate Video

Return to posts index

charlie hughesRe: ram leak
by on Jan 27, 2011 at 1:26:33 am

All I am doing is opening a project film with the footage in it. I am not shuttling through the footage whatsoever, nor am I adding effects or anything like that. I can edit just fine while the RAM usage climbs but within a few minutes, regardless of what i'm doing, it grows to 100% and crashes.

Non responsive software, even windows explorer has trouble elsewhere.

I installed the K-light package but problem remains.

I have 12 gigs of ram, 8 core way too expensive machine for this nonsense.

Happens in after effects and premiere. Thanks to all your help with suggestions! I appreciate any help here.

Return to posts index

Graham MacfarlaneRe: ram leak
by on Jan 26, 2011 at 3:58:41 pm

Have you recently changed or updated any codecs on your system. Perhaps you could check for possible codec conflicts in the Win7 action center (flag icon - taskbar on the right normally)

If I ever get strange codec behaviour I found it was quicker (at least back in the XP days) to uninstall and reinstall a single codec pack rather than to find and fix codec / registry screw ups.

If you are not using a codec pack I would recommend the latest version K-lite!

Graham Macfarlane
3D animator and VFX specialist
London UK

Return to posts index

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
© 2017 All Rights Reserved