ID 515323 - A crash occurs when using the CurveTool node to analyze a blinkscript in Nuke

Problem summary
A crash occurs when using the CurveTool node to analyze a blinkscript in Nuke.
 
Customer reported version
Nuke 13.2v1
 
Customer reported platform
CentOS 7
 
Steps to reproduce
1) In Nuke, load any footage around 100+ frames.
2) Add a Blinkscript node, then compile the default Saturation kernel.
3) Select the KernelParamaters tab, then adjust the saturation level.
4) Add a CurveTool node, then select the Go! knob from the Properties bin.
5) Allow the frame range to be the length of the clip, then press OK and observe the results.
 

 
Alternative command line steps:
1) Download the attached .py file.
2) In Terminal/Command Prompt, path to the Nuke installation directory.
3) Run the command: ./Nuke -t path/to/file.py (where path/to/file.py is the downloaded attachment)
4) Observe the output from the command prompt.

 
Expected behavior
The command should complete and have no errors.
 
Actual behavior
On CentOS 7 the Terminal crashes with the following error:
 

*** Error in `./Nuke13.1': double free or corruption (!prev): 0x0000000005faa400 ***======= Backtrace: =========/lib64/libc.so.6(+0x81329)[0x7f36c0da7329]/usr/local/Nuke13.1v1/libDDImage.so(+0x21ad03)[0x7f36b6edad03]/usr/local/Nuke13.1v1/plugins/CurveTool.so(+0x68e9)[0x7f3684dc88e9]/usr/local/Nuke13.1v1/libtbb.so.2(+0x2f4ef)[0x7f36b3fa44ef]/usr/local/Nuke13.1v1/libtbb.so.2(+0x28ae4)[0x7f36b3f9dae4]/usr/local/Nuke13.1v1/libtbb.so.2(+0x27603)[0x7f36b3f9c603]/usr/local/Nuke13.1v1/libtbb.so.2(+0x23846)[0x7f36b3f98846]/usr/local/Nuke13.1v1/libtbb.so.2(+0x23a79)[0x7f36b3f98a79]/lib64/libpthread.so.0(+0x7ea5)[0x7f36c1b20ea5]/lib64/libc.so.6(clone+0x6d)[0x7f36c0e249fd]

On Windows 10, the console output abruptly stops (crashes), but does not have any errors. When running the custom.py script in Script Editor from the GUI on CentOS 7 and Windows 10, it renders a few frames and then crashes with the Crash Reporter dialog prompt sometimes appearing. 
 
 
Workaround
There is no available workaround at this time.
 
Reproduced by Support in:
Nuke 13.2v3 - CentOS 7, Windows 10
Nuke 13.2v1 - CentOS 7
Nuke 13.1v1 - CentOS 7, Windows 10 - regression
 
Unable to reproduce bug in:
Nuke 13.0v8 - CentOS 7, Windows 10
 
Earliest version tested
Nuke 13.0v8 - This issue doesn't appear in this version and has regressed