ID 563460 - Nuke exits when opening a script, containing nodes with expression linked lifetime knobs, in terminal mode

Problem summary
Nuke exits when opening a script, containing nodes with expression linked lifetime knobs, in terminal mode.

Customer reported version
Nuke 12.2v10

Customer reported platform
CentOS 7

Steps to reproduce

1) Open Nuke.

2) Create 2 seperate Blur nodes.

3) Select Blur1 and execute the following code in the Script Editor:

nuke.selectedNode()["lifetimeStart"].setExpression("Blur2.lifetimeStart")nuke.selectedNode()["lifetimeEnd"].setExpression("Blur2.lifetimeEnd")nuke.selectedNode()["useLifetime"].setExpression("Blur2.useLifetime")

Alternatively, paste the following script into the Node Graph:

Blur { inputs 0 name Blur1 xpos 149 ypos -82 mix {{Blur2.mix}} lifetimeStart {{Blur2.lifetimeStart}} lifetimeEnd {{Blur2.lifetimeEnd}} useLifetime {{Blur2.useLifetime}}}Blur { inputs 0 mix 0.845 name Blur2 selected true xpos -72 ypos -89}

4) Save the script.

5) Open the script in command line. For example:

"C:\Program Files\Nuke15.0v2\Nuke15.0.exe" -ti C:\temp\script.nk

Expected behaviour
The script should open in command line.

Actual behaviour
The script throws errors like so, and the command line session quits:

[14:30.02] ERROR: Blur1.lifetimeStart: Nothing is named "Blur2"[14:30.02] ERROR: Blur1.lifetimeEnd: Nothing is named "Blur2"[14:30.02] ERROR: Blur1.useLifetime: Nothing is named "Blur2"Blur1.lifetimeStart: Nothing is named "Blur2"Blur1.lifetimeEnd: Nothing is named "Blur2"Blur1.useLifetime: Nothing is named "Blur2"

Workaround
Unknown.

Reproduced by support
This bug has been reproduced in:
Nuke 15.0v2 - Windows 10

Nuke 12.0v1 - Windows 10

Nuke 10.0v1 - Windows 10

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

We're sorry to hear that

Please tell us why