ID 602582 - Nuke can create scripts which cannot be opened when certain BlinkScript nodes that use abs functions are present

Follow
  1. The Foundry SANDBOX
  2. Bug Tracker
  3. Nuke

Problem summary:
Nuke can create scripts which cannot be opened when certain BlinkScript nodes that use abs functions are present
 
It appears that although only some Nuke versions can create these corrupt files, once the file is created future versions of Nuke will hang when attempting to open it.
 
Customer reported version:
Nuke 15.2v2
 
Customer reported platform:
Rocky 9
 
Steps to reproduce:
1) Download the attached original_file_14.0.nk file and launch one of the affected versions of Nuke, such as 15.2v4
2) Open the original_file_14.0.nk and navigate to File > Save Comp As... 
3) Save a new file, and name it new_file_15.2.nk or similar
4) Navigate to File > Clear, then File > Open Comp...
5) Select the file created in step 3, and observe Nuke's performance 
 
Alternative steps:
1) Download the attached new_file_15.2.nk and launch Nuke 15.2 or above
2) Attempt to open the file via File > Open Comp..., and observe Nuke's performance
 
Expected behavior:
A BlinkScript kernel which cannot compile should not prevent the entire .nk Nuke script from opening.
 
Actual behavior:
When a Nuke script that contains BlinkScript nodes that use abs() is opened in a more recent version of Nuke, saving the Nuke script can result in a file which can no longer be opened. 
 
Workaround:
Replacing all instances of abs() inside the original file's BlinkScript nodes with fabs() seems to prevent the issue from occurring.
 
Reproduced by Support in:
Nuke 15.2v4 - Windows 11, macOS 14 Sonoma
Nuke 15.2v1 - Windows 11
Nuke 15.1v8 - Windows 11
Nuke 15.1v7 - macOS 14 Sonoma -- Regression
Nuke 15.1v5 - Windows 11 -- Regression
 
Unable to reproduce bug in:
Nuke 16.0v4 - Windows 11, macOS 14 Sonoma
Nuke 16.0v1 - Windows 11
Nuke 15.1v6 - macOS 14 Sonoma
Nuke 15.1v5 - macOS 14 Sonoma
Nuke 15.1v4 - Windows 11
Nuke 15.1v1 - Windows 11
 
 
Earliest version tested:
Nuke 15.1v4 - This issue doesn't appear in this version and has regressed

    We're sorry to hear that

    Please tell us why