8736892565
As the value of the askForRendererKill flag is set right after the return of the kill process, under some particular memory and system load circumstances, a race condition occurs and the rendering process in the main thread is closed faster than the process.destroy() returns the control to the thread the called the OS.getOS().kill(process.getProcess()) method. If that condition occurs, the isAskForRendererKill() check returns false (the flag hasn't been set to True in the separate thread) and the execution continues with the frame output check (that doesn't exist as the rendering process was interrupted). The final outcome is a wrong NO_FILE_OUTPUT error instead of the proper RENDERER_KILLED_BY_USER_OVER_TIME. The fix has been setting the askForRendererKill flag to true before the process is destroyed. If the racing condition occurs, the askForRendererKill will be correctly set.
SheepIt Render Farm Client
Overview
SheepIt Render Farm Client is an Open Source client for the distributed render farm SheepIt.
Compilation
You will need Java 1.7 or higher. (OpenJDK and Oracle are both supported).
To create the jar file, simply type ./gradlew shadowJar on linux/OSX and gradlew.bat shadowJar on Windows in the project's root directory.
Usage
Once you have the jar file, you can see how to use it by running:
java -jar build/libs/sheepit-client.jar --help
When you are doing development work, you can use a mirror of the main site specially made for demo/dev. The mirror is located at http://sandbox.sheepit-renderfarm.com, and you can use it by passing -server http://sandbox.sheepit-renderfarm.com to your invocation of the client.
At the command line ui (-ui text / -ui oneLine) you could type in the following commands and press enter to control the client:
- status: get the current status of the client (paused, stoped, etc.)
- priority : set the renderer process priority
- block: block the current project
- pause: pause the client to request new jobs after the current frame has finished to render
- resume: resume the client after it was paused
- stop: stop the client after the current frame has finished
- cancel: cancel the stop request
- quit: stop the client directly without finishing the current frame