On 2010-06-17 21:49:08 -0400, Greg Ercolano said:
Yes, this is really annoying, details on that were posted
here on the group a few months ago here:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1906+1906
This cropped up because Adobe made a change in CS3 that causes the
render process to disconnect itself from the process hierarchy,
effectively orphaning the process.
Adobe is aware of the problem as of November 2009, and is trying
to fix it. I worked directly with the AE devs on that issue.
The AE engineers came up with a javascript mod as a temporary
workaround to solve the problem; I can try to follow up with
those engineers through myself on your behalf; contact me off list.
This can be replicated from the command line as well by just
running aerender interactively, and then killing it.
You don't have to reboot to fix the problem, you can do something
like a 'killall' command as root to kill the aerendercore and
associated processes.
Until Adobe fixes this, all render queue systems and distributed scripting
of AE is affected by this.
Have you received any updates as to when, or if, this might be
corrected in CS5? It appears that the issue is still around.
If not, what sort of measures have you implemented to determining that
renders have actually completed (when you receive false negatives or
positives from aerender)? So far, I've been watching the status
returned by the aerender process and monitoring the log file it creates
to determine when the render is complete, but that doesn't seem to be
completely reliable.
We're running multiple instances of aerender on a single machine so a
"killall" against aerendercore, when it hangs, isn't an option.
|