ID 554969 - SplineWarp nodes using certain formats can cause Nuke to crash on specific frames

Problem summary:
SplineWarp nodes using certain formats can cause Nuke to crash on specific frames 
 
Customer reported version:
Nuke 13.2v8
 
Customer reported platform:
CentOS 7
 
Steps to reproduce:
1) Launch Nuke and open the attached crash_demo.nk file.
2) View the SplineWarp node, and scrub to frame 1073.
3) Observe Nuke's performance.
 
Expected behavior:
The SplineWarp node should display frame 1073 without affecting Nuke's stability.
 
Actual behavior:
While using certain formats, like 4608x3264, Nuke will crash when viewing the SplineWarp node at frame 1073.
 
Workaround:
Changing the format to be one pixel greater (4608x3264 -> 4609x3265) seems to prevent the crash from occurring. Alternatively, turning off hard boundary in the SplineWarp node also seems to prevent the crash:

In some circumstances, turning off the SplineWarp's bbox boundary curve knob might allow the initial crashing frame to display correctly, but there's a possibility that Nuke may crash at a different frame instead. 
 
Reproduced by Support in:
Nuke 14.0v6 - Windows 10, CentOS 7
Nuke 14.0v1 - Windows 10
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10, CentOS 7
 
Earliest version tested:
Nuke 11.0v1 - This issue appears to be in all tested versions of the product