|
this is all well and good, but what could possibly cause this 'release of semiphore' and how to stop it happening. It happens on single licence machines (at home) as well as network farm renders. Could it be multithreading hardware related or is it just MR being crap. (again)
On 29/10/2007, Hajo ten Thije <ten(at)entec.de> wrote:
Hi Eric,
your Hovercraft is just a kind of mini file (sign), which is written to
the render directory to tell other machines that the computation of a
specific frame is currently going on, but the image has not been written
to disk so far. So, the semaphore "gives sign" other processors to
compute the next, not yet existing frame of the current renderjob.
Semaphores are write protected and hidden. If the release of a S. failes
(for what reason?!) it could result in the specific error message.
Hajo
http://en.wikipedia.org/wiki/Semaphore
sounds like
Eric Lampi schrieb:
> What does this mean? I crashed my render.
>
> DB 0.17 fatal 041264: ReleaseSemaphore failed - The handle is invalid.
>
>
> It makes as much sense to me as:
>
> DB 0.19
fatal 04293: MyHovercraftIsFullofEels failed - Crunchy Frog
>
> Thanks,
>
> E
>
> Freelance 3-D Animator, F/X Artist
>
>
---
Unsubscribe? Mail
Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
|
