ID 485336 - Nuke sometimes crashes when rendering with 128 threads or more

Problem summary
Nuke sometimes crashes when rendering with 128 threads or more

Customer reported version
nuke.13.0v2

Customer reported platform
centos7

Steps to reproduce

1) Download the attached crash.nk and crash.exr and save to the same folder

2) Render with Nuke using the following command:

 /usr/local/Nuke13.0v2/Nuke13.0 --safe -t -x -F 1-10 -i /path/to/crash.nk 

3) Sometimes when Nuke renders it will segfault:

/usr/local/Nuke13.0v2/Nuke13.0 --safe -t -x -F 1-10 -i crash.nk 
Nuke 13.0v2, 64 bit, built Apr 26 2021.
Copyright (c) 2021 The Foundry Visionmongers Ltd.  All Rights Reserved.
[14:41.04] Warning: Could not find value "acescg" for "colorspace". It will be appended to the menu list.
[14:41.04] Warning: Could not find value "art" for "colorspace". It will be appended to the menu list.
Writing /home/nikolaos.koutsikos/Desktop/testrender.mov took 0.19 seconds
Frame 1 (1 of 10)
....
Writing /home/nikolaos.koutsikos/Desktop/testrender.mov took 0.01 seconds
Frame 10 (10 of 10)
Total render time: 0.32 seconds
[nikolaos.koutsikos@TR3 Desktop]$ /usr/local/Nuke13.0v2/Nuke13.0 --safe -t -x -F 1-10 -i crash.nk 
​Nuke 13.0v2, 64 bit, built Apr 26 2021.
Copyright (c) 2021 The Foundry Visionmongers Ltd.  All Rights Reserved.
Segmentation fault (core dumped)​

Expected behaviour
For Nuke to render successfully every time

Actual behaviour
Nuke crashes

Workaround
Use -m to limit Nuke to use less threads

Reproduced by support
This bug has been reproduced by the developers in:
Nuke 13.0v2 - CentOS - Threadripper 3990X

Unable to reproduce:
Threadripper 3970X
Dual Intel Xeon E5-2678W