ID 386609 - Dope Sheet crashes Nuke when a script is saved, cleared and reloaded after a previously moved keyframe is altered again.

Follow

Problem summary
When using the Dope Sheet, if you move a node's keyframe value, save then clear the script, upon opening the script again and moving the keyframe values in the Dope Sheet, Nuke will crash.

From our testing this occurs with any nodes, only when the comp session remains open and not within the Windows operating system

Note: Linux and MacOS only issue

Customer reported version
nuke.11.3v2

Customer reported platform
10.12

Steps to reproduce

1) Open a new Nuke script on a Mac or Linux machine

2) Set the Viewer to frame 10

3) Create a Merge node

4) Within the Merge node, key the mix value at 1 (this key is needed for the Dope Sheet to access the node)

5) With the Merge node still selected, open the Dope Sheet Tab and highlight the Merge1 to show the keyframes

6) With the Merge1 highlighted, type in -1 into the field and press Move. This will move the keyframe from 10 to 9


7) Save the script and clear/close the comp, ensuring the Nuke session stays open.

8) Re-open the script and double click the Merge node

9) Open up the Dope Sheet and either highlight the keyframes or press the Move button
Result: Nuke crashes

Expected behaviour
Nuke should not crash when the Dope Sheet is opened in an active Nuke session

Actual behaviour
Nuke crashes when the Dope Sheet is opened in an active Nuke session

Workaround
Unfortunately, the only workaround we found was the close the Nuke session and re-open a new Nuke session. This clears the Dope Sheet back to 0 and the error does not occur.

Reproduced by support
This bug has been reproduced in:
Nuke 11.3v2 - MacOS 10.13.6 - CentOS 7
Nuke 11.2v5 - MacOS 10.13.6
Nuke 11.2v1 - MacOS 10.13.6
Nuke 11.1v1 - MacOS 10.13.6
Nuke 11.0v1 - MacOS 10.13.6
Nuke 10.5v1 - MacOS 10.13.6
Nuke 10.0v1 - MacOS 10.13.6
Nuke 9.0v1 - MacOS 10.13.6
Nuke 8.0v1 - MacOS 10.13.6 - CentOS 7

Unable to reproduce bug in:
Nuke 11.3v2 - Windows 7
Nuke 8.0v1 - Windows 7

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

    We're sorry to hear that

    Please tell us why