We’ve been running into a few
Object reference not set to an instance of an object in our Katana tasks in our Deadline 10.0.20.2.
For some unknown reason, a new “Render task” is sometimes spawned right after the Katana render task has successfully completed (not limited to a frame, job, node or particular time).
It then fails, which resulted in the entire task in the Monitor showing up as failed, even though the Katana render successfully completed
Here’s a few snippets from a render log:
Object reference not set to an instance of an object
at Deadline.Plugins.SandboxedPlugin.d (Deadline.Net.DeadlineMessage aoa) [0x00242] in :0
at Deadline.Plugins.SandboxedPlugin.RenderTask (System.String taskId, System.Int32 startFrame, System.Int32 endFrame) [0x000df] in :0
at Deadline.Slaves.SlaveRenderThread.c (Deadline.IO.TaskLogWriter aek) [0x0073e] in :0
(At the end of the) Log
2019-02-11 11:23:04: 0: STDOUT: [INFO python.RenderLog]: Complete.
2019-02-11 11:23:05: 0: STDOUT: [INFO python.MainBatch]: Katana2D Render Progress: 100% – 11:23:04 AM Mon 11-Feb-19
2019-02-11 11:23:05: 0: STDOUT: [INFO python.MainBatch]: Frame 1142 completed in 15:01:51.5s
2019-02-11 11:23:05: 0: INFO: Process exit code: 0
2019-02-11 11:23:05: 0: Done executing plugin command of type ‘Render Task’
2019-02-11 11:23:05: 0: Encountered an error while executing plugin command of type ‘Render Task’
Has anyone come across similar issues or know what might be causing it?
Full log: katana_render_task_error.py (70.0 KB)