ID 585906 - Nuke crashes when zooming the Viewer in/out if a ScanlineRender node that uses certain filtering options with transparent images outputs Deep data and is merged with another ScanlineRender

Problem summary:
Nuke crashes when zooming the Viewer in/out if a ScanlineRender node that uses certain filtering options with transparent images outputs Deep data and is merged with another ScanlineRender
 
This issue does not appear to affect the New 3D System nodes, as the ScanlineRender2 node does not have Nearest, Bilinear, Trilinear, or Anisotropic filtering options.
 
Customer reported version:
Nuke 14.1v2
 
Customer reported platform:
Windows 10
 
Steps to reproduce:
1) Download the attached crash_demo.nk file and launch Nuke.
2) Open the file and View the Merge1 node.
3) Double-click the ScanlineRender2 node to open its Properties.
4) Change the filter knob to any of the following options: Nearest, Bilinear, Trilinear, or Anisotropic
5) Use the scroll wheel in the Viewer to zoom in/out, and observe Nuke's performance:

 
 
Expected behavior:
Nuke should remain stable when zooming the Viewer in or out.
 
Actual behavior:
In node setups where a ScanlineRender has an input with transparent images/textures, outputs some Deep data, and is then Merged with another ScanlineRender, Nuke will crash if the ScanlineRender node has been set to use Nearest, Bilinear, Trilinear, or Anisotropic filtering modes.
 
It has also been observed that occasionally this issue will cause Nuke to produce multiple crash reports, sometimes 10 or more.
 
Workaround:
In addition to not using the affected filtering modes (Nearest, Bilinear, Trilinear, or Anisotropic), adding a DeepToImage node after the ScanlineRender1 node also seems to prevent the crash:

 
Reproduced by Support in:
Nuke 15.1v2 - Windows 10, macOS 14 Sonoma
Nuke 14.0v1 - Windows 10
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
 
Earliest version tested:
Nuke 12.0v1 - This issue appears to be in all tested versions of the product