Problem summary
Nuke stops rendering after a couple of frames in terminal mode for certain Nuke scripts
This example Nuke scripts contains clones, expressions, Python expressions on Knobs and expression based Read nodes which all seem to impact this performance.
Starting at earlier frames, like 1015, the render gets stuck on the second frame, but starting at 1018, then render completes.
This doesn't happen in the GUI, unless you launch Nuke with -n, disabling postage stamps, and not using a Viewer, preventing any of the images being pre-loaded.
Customer reported version
nuke.12.2v8
Customer reported platform
centos7
Steps to reproduce
1) Open Terminal
2) Run the following command:
usr/local/Nuke12.2v8/Nuke12.2 -t -V 2 -X out --view main /mnt/netshare/support/tickets/132564/scene_exemple/workfile/nukeRenderStopsBug.nk 1017,1031,1
Nuke will render frame 1017, but get stuck when writing 1018:
Testing this for multiple days, the render progress never increases, and the CPU usage bounces around 100% (1 thread fully used), and the RAM usage stays about the same.
Expected behaviour
For Nuke to render additional frames.
Actual behaviour
Nuke stops rendering after some frames.
From internal testing, this happened after the first frame, for the customer, this happens on the third of fourth frame.
Workaround
Unknown
Reproduced by support
This bug has been reproduced in:
Nuke 13.2v5 - CentOS 7
Nuke 13.0v3 - CentOS 7 - regression in 13.0
Nuke 12.2v8 - CentOS 7 - regression in 12.2
Unable to reproduce bug in:
Nuke 13.2v5 - Windows 10, macOS Monterey
Nuke 13.0v2 - CentOS 7
Nuke 12.2v7 - CentOS 7
Earliest version tested
Nuke 12.2v7 - This issue doesn't appear in this version and has regressed
