State:New|TargetRelease:No Target|icon_bug|icon_nuke|database:public|Resolution:Fixed|BugID:383047|
Problem summary
Nuke crashes after rendering an odd number of .exrs in terminal mode when the script queries the file metadata in an OCIO context knob and contains an OFX node, like the old OFlow node or a F_ReGrain node.
On Linux, after rendering the terminal returns a segfault/crashes
On Mac, after rendering Nuke crashes and OSX shows a warning
On Windows, there is a long pause before the Command Prompt returns to user control
Customer reported version
nuke.11.2v5
Customer reported platform
centos7
Steps to reproduce
1) Download the attach Nuke script and .mov to the same directory
2) Render the Nuke script using the below command in a console window:
<path/to/nukeInstall> --safe -x -F 11-13 <path/to/nuke/script.nk>
3) Nuke will crash/hang after rendering
Workaround
Use the other type of OFlow node, or render another file format, or render an even number of frames
Reproduced by support
This bug has been reproduced in:
Nuke 11.3v2 - CentOS 6.9 - Windows 10 - MacOSX 10.13
Nuke 11.2v1 - CentOS 6.9
Nuke 11.1v3 - CentOS 6.9 - Windows 10 - MacOSX 10.13 - regression
Unable to reproduce bug in:
Nuke 11.1v2 - CentOS 6.9 - Windows 10 - MacOSX 10.13
Earliest version tested
Nuke 11.1v2 - This issue no longer appears in this version and has regressed
Expected behaviour
For Nuke to close after rendering
Actual behaviour
It crashed / hangs after rendering
We're sorry to hear that
Please tell us why