This problem is Mac OSX specific, and is happening with CS4.
It might be happening with CS3 as well, I haven't checked.
It has come to my attention that After Effects CS4's 'aerender'
program is now invoking AfterFx in a way where AfterFx no longer
remains part of the process hierarchy, making it immune to receiving
kill signals from normal process group management.
So when you requeue busy frames, or dump a running After Effects job,
the After Effects process remains running.
In the case of rush, the frames show in the Die state, and don't immediately
transition to Que until the AfterFx process finishes rendering the frame
it's working on.
Other render queues have trouble with this as well.
Even scripts that are interrupted with ^C can leave AfterFx running
in the background, taking up CPU.
Apparently when aerender starts AfterFx, the AfterFx process becomes
parented to launchd, and is no longer parented to the aerender process.
I've notified Adobe, and they're working on a solution.
|