ID 336204 - Nuke failing to render when running more than 64 threads

Problem summary
Nuke fails to render the following script when Nuke is running more than 64 threads. This only appears to happen on Linux.
This occurs when rendering either from GUI or from the terminal.

Customer reported version
nuke.11.1v1

Customer reported platform
centos7

Steps to reproduce

Firstly, this bug can be reproduced in GUI mode with the following steps:

1) Open Nuke 

2) Open the attached .nk script.

3) Double click the Write node to open its Properties pane, and click Render. On the dialog that appears, uncheck 'Continue on error' and click OK. Notice that the render 'hangs' and does not complete.


The bug can also be reproduced when rendering from the terminal:

1) Open the Terminal and run the following command:

/usr/local/Nuke11.1v1/Nuke11.1 -V 2 -x -F first_frame_number - last_frame_number /fileppath/filename

2) Notice that the render 'hangs' and does not complete.

Workaround
Use the -m flag when launching Nuke or when rendering from the terminal and limit the number of threads to 64, for example:

/usr/local/Nuke11.1v1/Nuke11.1 -m 64 -V 2 -x -F first_frame_number - last_frame_number /fileppath/filename

Reproduced by Support in:
Nuke 12.2v5 - Linux CentOS 7
Nuke 11.1v2 - Linux CentOS 6
Nuke 11.0v1 - Linux CentOS 6
Nuke 10.0v1 - Linux CentOS 6
Nuke 9.0v9 - Linux CentOS 6
Nuke 9.0v1 - Linux CentOS 6 - Regression

Unable to reproduce bug in:
Nuke11.1v2 - Windows 10
Nuke 8.0v7 - Linux CentOS 6

Have not been able to test on Mac OSX due to not having access to a Mac with more than 64 threads.

Earliest version tested
Nuke11.1v2 - Windows 10
Nuke 8.0v7 - Linux CentOS 6
- This issue no longer appears in this version and has regressed. This may be due to changes that were made to the VectorBlur node in later versions of Nuke.

Expected behaviour
The attached script should render in GUI or Terminal mode.

Actual behaviour
The attached script fails to render in GUI or Terminal mode.