Problem summary Our user has received an issue, where their SplineWarp key has become corrupted.
WINDOWS: With the script opened, viewing the SplineWarp node and switching to "frame 1096" causes Nuke to freeze and display image information into the Viewer:
Clicking somewhere in Nuke will cause it to freeze, although leaving it for a long while will bring it back.
LINUX/MAC With the script opened, viewing the SplineWarp node and switching to "frame 1096" crashes Nuke.
Customer reported version nuke.11.3v4
Customer reported platform windows10
Steps to reproduce
LINUX/MAC Reproduction:
1) Open the attached script,
2) Navigate to Frame 1096 and view the 'Ear' node.
Result: Nuke crashes to desktop
WINDOWS Reproduction:
1) Open the attached script
2) Navigate to Frame 1096 and view the 'Ear' node.
Result 1: Nuke will freeze and start repeating numbers within the Terminal Window. After a while, Nuke will become responsive again.
3) Once Nuke is responsive, switch to another frame and wait.
4) Once responsive, switch the Viewer to the Constant node.
5) Double click the 'Ear' node to display it in the Properties bar, and scrub over the timeline.
Result 2: The SplineWarp will transition as expected, but is broken on frame 1096 The Viewer does not freeze as it isn't viewing the SplineWarp
Expected behaviour The SplineWarp frame should not be corrupted.
Actual behaviour The SplineWarp has a corrupted frame, causes render crashes.
Workaround Deleting the animation on frame 1096 from the SplineWarp resolves the issue.
Reproduced by support
This bug has been reproduced in: Nuke11.3v1- Windows 7 - Mac10.14 - CentOS7 Nuke11.3v1- Windows 7 - Mac10.14 - CentOS7 Nuke11.2v1 - Windows 7 Nuke11.1v1 - Windows 7 Nuke11.0v1 - Windows 7 Nuke10.5v1 - Windows 7 Nuke10.0v1 - Windows 7 Nuke9.0v1 - Windows 7 Nuke8.0v1 - Windows 7 - Mac10.14 - CentOS7
Earliest version tested - This issue appears to be in all versions of the product
