ID 165068 - ScanlineRender - bad allocation with Spherical projection mode

Problem summary
Customer is getting an error message ‘ScanlineRender : Bad Allocation’ when looking through the Scanline Renderer after using the C_SphericalTransform node in the tree after heavy geometry that has high res textures as inputs

Customer reported version
nuke.10.5v3

Customer reported platform
windows10

Steps to reproduce

1) Import three or more large .abc or .obj geo files through ReadGeo nodes

2) Read in several high resolution (8k) images (I used jpg’s) and use input to the geometry

3) Create a Scene node and plug the abc/obj files

4) Create a Scanline Render node and connect into the Scene node

5) Create a Camera and connect in the Scanline Renderer

6) Add in C_SphericalTranform node

7) Look through C_SphericalTransform node.

Result: Error Message ‘ScanlineRender : Bad Allocation’

Workaround
Two workaround options:

1) Reduce the amount of Max Tessellation in the Scanline Render properties. Reducing this will lessen the amount of subdividing geometry being read

2) Use the C_RayRender node as appose to the Scanline Renderer node as it is optimised for rendering spherical cameras

Reproduced by support
Problem has been reproduced in Windows 7, could not reproduce in Mac OSX

In which versions have you reproduced the problem?

Windows 7 - Nuke 10.5v4

Windows 7 - Nuke 10.0v1

Expected behaviour
Scanline renderer’s memory buffer should not break

Actual behaviour
Scanline renderer can’t handle large geometry with large texture files and spherical transforms together and overloads the Scanline memory buffer