ID 416367 - VectorGenerator causes CUDA error when motionEstimation is local, and the input has a boundingbox different to the format, which can cause Nuke to crash

Problem summary
VectorGenerator causes CUDA error when motionEstimation is local, and the input has a boundingbox different to the format, which can cause Nuke to crash

It errors in the Viewer saying: VectorGenerator1: CUDA Error: Unknown Error code: 700

In the terminal it says: A CUDA error occurred. Please restart to continue.

After the error, changing frame will freeze/hang/crash Nuke without a crash report dialog

This only effects Windows

Customer reported version
nuke.n/a

Customer reported platform
windows10

Steps to reproduce

1) Open NukeX
2) Paste the below script

CheckerBoard2 {
 inputs 0
 name CheckerBoard1
 selected true
 xpos 168
 ypos -168
}
Crop {
 box {520 335 1610 1185}
 name Crop1
 selected true
 xpos 168
 ypos -96
}
VectorGenerator {
 name VectorGenerator1
 selected true
 xpos 168
 ypos -70
}

3) View VectorGenerator and view the motion channel, the node will error:

6) Change frame, Nuke will freeze/hang/crash without a crash report dialog

Expected behaviour
For the motion vectors to be viewed

Actual behaviour
The node errored, then crashed Nuke

Workaround
Add a Reformat node with black outside enabled before the VectorGenerator

Reproduced by support

This bug has been reproduced in:
Nuke 12.0v3 - Windows 10 

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

Unable to reproduce bug in:
Nuke 12.0v3 - CentOS 7.7 - MacOSX 10.13

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