ID 385453 - Animating a custom channel to 0 while viewing a Defocus node causes crash

Follow

Problem summary
When adding a custom channel to a Defocus node through a Merge and Shuffle node, if the Merge node's mix is set to 0 while viewing the new channel, Nuke crashes to desktop.

Tests on other nodes did not display this behaviour ( Tests on ZDefocus, Grade, Denoise ).

Additionally, the issue only occurs when playing through the footage when it is keyed to 0.
Manually setting the value to 0 does not display a crash.  

Customer reported version
nuke.11.2v5

Customer reported platform
windows10

Steps to reproduce

1) Open Nuke

2) Create a Checkerboard node

3) Create a Shuffle node and set up a new channel like follows:


4) Merge your Shuffle back into your Roto node

5) Create a Defocus node under the Merge

Your Node Graph Should look like the following:

​​

​​

 

6) Within the Merge node, key the 'mix' over a few frames from '1 to 0'

7) Within the Merge, set the 'also merge' to the new channel:


8) Save, then play through the Nuke Timeline at the Defocus Node.

Result: Nuke should crash to desktop.

 If nuke does not crash, reopen the project and play from the Defocus node.

 
Please NOTE: This issue also occurs when Rendering if the Write node is specifically set to the custom channel.
                         Rendering with 'All' channels works as expected.

Expected behaviour
The channel should fade out when the mix hits 0

Actual behaviour
Nuke Crashes to desktop

Workaround
If you need to hide the channel, set the value to 0.001

Reproduced by support

This bug has been reproduced in:
Nuke11.3v1- Windows 7 - Mac10.13 - 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.13 - CentOS7

Earliest version tested
- This issue appears to be in all versions of the product

Any customer specific info and messages should go below here to be added as an internal comment in TP:

    We're sorry to hear that

    Please tell us why