ID 606626 - Not all bounding box pixels are preserved when large images are scaled up

Problem summary:
Not all bounding box pixels are preserved when large images are scaled up
 
Customer reported version:
Nuke 15.0v5
 
Customer reported platform:
Windows 11
 
Steps to reproduce:
1) Download the attached large_format_test.nk file, then open this script in Nuke
2) View the Transform1 node, and observe how the image can be freely translated/scaled and pixels in the bounding box are retained:

3) View the Crop1 node, which is set to reformat the image to match its entire bounding box
4) Note that the left and right sides of the image are missing and have been replaced with stretched pixels:
 

 
Expected behavior:
Pixels outside of the image format should be preserved as the total image size including the bounding box is below Nuke's maximum pixel count of 2^32
 
Actual behavior:
Past a certain size, pixels in the bounding box that are outside the image format can be lost and no longer be available to downstream nodes. This can produce unexpected and inconsistent results when attempting to use the bbox pixels in 3D projection workflows for example.
 
Workaround:
No known workaround at this time.
 
Reproduced by Support in:
Nuke 16.0v5 - Windows 11, macOS 14 Sonoma
Nuke 15.0v1 - Windows 11
Nuke 14.0v1 - Windows 11
Nuke 13.0v1 - Windows 11
 
Earliest version tested:
Nuke 13.0v1 - This issue appears to be in all tested versions of the product