Nuke crashes when altering the values on a ColorCorrect node if its lookup knob is expression-linked
This also affects DeepColorCorrect nodes.
Customer reported version:
Nuke 12.2v9
Customer reported platform:
CentOS 7
Steps to reproduce:
1) Launch Nuke and create a Checkerboard node.
2) Create a ColorCorrect node and deselect it by clicking on the empty space in the Node Graph.
3) Create a Blur node and close its Properties bin.
4) In the ColorCorrect1 node's Properties, open the Ranges tab.
5) Right-click anywhere on the curves and select Edit > Edit Expression
6) Paste Blur1.size into the shadow field and click OK:
7) View the ColorCorrect1 node and switch to its ColorCorrect tab.
8) Observe Nuke's performance while scrubbing or entering values into any knob under shadows, midtones, or highlights.
Expected behavior:
Nuke should remain stable when changing the knobs on a ColorCorrect node.
Actual behavior:
Changing the values on a ColorCorrect node after expression linking its lookup knob causes Nuke to print an error like the one below, and then crash. This seems to happen when the ColorCorrect1 node is expression linked to any knob, but the following nodes were specifically tested: AddMix, ColorCorrect, Sampler, CrossTalk, DeepColorCorrect, Root, and HueCorrect.
[18:41.45] ERROR: ColorCorrect1.lookup: recursive expression in Blur1.size[18:41.45] ERROR: ColorCorrect1.lookup: recursive expression in Blur1.size[18:41.46] ERROR: ColorCorrect1.lookup:alloc: invalid block: 0x7f6d6800f3c0: 30 6c ef
Additionally, Nuke will crash if the expression linked curve is pointing to itself. For example, editing the expression of ColorCorrect1 to be this.shadow or ColorCorrect1.lookup.shadow will exhibit the same behavior as linking the expression to a knob on a separate node.
Workaround:
No known workaround at this time.
Reproduced by Support in:
Nuke 14.0v3 - Windows 10, CentOS 7
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.0v1 - Windows 10, CentOS 7
Earliest version tested:
Nuke 10.0v1 - This issue appears to be in all tested versions of the product
