Problem summary
Running nuke.execute() in the Nuke 12.2 Python interpreter results in a crash.
The issue only appears to happen when reading EXR sequences.
Customer reported version
Nuke 12.2v5
Customer reported platform
CentOS 7
Steps to reproduce
1) Download the attached .nk script (script.nk). It contains a Read node, which is loading in an EXR sequence, and a Write node with all knobs set to the default values:
2) Save the following code into a Python (.py) file:
NK_SCRIPT = "./script.nk"import nukenuke.scriptOpen(NK_SCRIPT)node = nuke.toNode("Write1")output = "/tmp/bug_test/output.####.exr" #change to an appropriate pathnode['file'].setValue(output)frame_range = (991, 1001)nuke.execute(node, frame_range[0], frame_range[1], 1)
The Python and .nk scripts should be saved within the same directory.
3) Open a Terminal session and navigate to the directory where your .nk and Python scripts are saved:
cd /path/to_some/folder
4) Execute the Python code with the following command (where nuke_execute.py is the name of your Python file):
/usr/local/Nuke12.2v9/python nuke_execute.py
RESULT:
Expected behaviour
The code should be executed and render out an EXR sequence.
Actual behaviour
Executing the code in the Nuke 12.2 Python interpreter results in a crash.
Workaround
The issue does not appear to happen in terminal mode:
/usr/local/Nuke12.2v9/Nuke12.2 -t nuke_execute.py
Reproduced by support
This bug has been reproduced in:
Nuke 12.2v9 - Linux CentOS 7
Nuke 12.2v4 - Linux CentOS 7 - Regression
Unable to reproduce bug in:
Nuke 12.2v9 - Windows 10
Nuke 12.2v3 - Linux CentOS 7
Earliest version tested
Nuke 12.2v9 - Windows 10
Nuke 12.2v3 - Linux CentOS 7
- This issue doesn't appear in this version and has regressed
