ID 389691 - A fatal crash occurs when triggering an Erode(filter) node while an Errored Read node is upstream.

Problem summary:
A fatal crash occurs when triggering an Erode (filter) node while an Errored Read node is upstream.

Customer reported version:
nuke.11.3v3

Customer reported platform:
centos7

Steps to reproduce:
1) In Nuke, create a Read node with any text to have it say ERROR in red. (i.e "tmp/test_##.jpg")

2) Create an Erode(filter) with channels set to rgba, attached to the Read node.

3) Add a Write node and enable the Postage Stamp setting (Alt+P).

4) Set the Viewer for the Write node to view the output.

5) Create a Constant node, but leave it unattached.

6) Trigger the Erode(filter) node in any way and observe stability in Nuke. This can be done by changing the Read node's file type and pressing Enter.

Expected behavior:
The script should remain stable and should continue processing any results.

Actual behavior:
Nuke fatally crashes when triggering the Erode(filter) node with an errored Read node upstream with a Constant node in the script. This can happen after changing the file type of the Read node, or by selecting Proxy mode in the Viewer (Ctrl+P).

Workaround:
There is no available workaround at this time.

Reproduced by Support in:
Nuke 11.3v3 - Windows 10, CentOS 7, macOS 10.13 High

Nuke 11.3v1 - Windows 10

Nuke 11.2v1 - Windows 10

Nuke 11.1v1 - Windows 10

Nuke 11.0v1 - Windows 10

Nuke 10.5v1 - Windows 10

Nuke 10.0v1 - Windows 10

Nuke 9.0v1 - Windows 10

Nuke 8.0v1 - Windows 10, CentOS 7, macOS 10.13 High Sierra

Earliest version tested:
Nuke 8.0v1 - This issue appears to be in all versions of the product