Nuke appcrash

Deadline
1

Hi Support,

We are getting a Nuke application crash on a renderbox. The slave doesnt seem to register the crash and still carrys on printing out commands that it is completing. However the task never completes and the slave seems to be stuck in an endless loop of printing out completed commands. Is there a function in the slave that should recognise the app crash error report and restart the task?..

I have attached a screenshot and hopefully all the details should be explained.

Marty

Nuke_crash_270510.JPG
Nuke_crash_270510.JPG1280×1024 102 KB

2

Hi Marty,

It looks like our Nuke plugin currently doesn’t have popup handling disabled. You can enable this by modifying the Nuke plugin. Open the file \your\repository\plugins\Nuke\Nuke.py in a text editor and find this line:

self.StdoutHandling = True

It should be in an InitializeProcess function past the halfway point of the file. Right above it, insert this line:

self.PopupHandling = True

Save the file, and you should be good to go. Note though that the slaves won’t recognize this change until they’re restarted or until they pick up a new Nuke job.

We’ll be sure to include this change in the upcoming release.

Cheers,

  • Ryan
3

Have followed these instructions but this doesnt seem to fix the problem.
Not sure if it is a huge issue having the popup but just eliminates it from being the cause of other issues…

4

I guess that’s just Windows’ crash dialog, which Deadline wouldn’t detect because it’s not being displayed by Nuke directly. Have you tried reinstalling Nuke on this machine to see if that helps? Or can you re-image the machine using an image from a working render box to see if that helps?

Cheers,

  • Ryan