ID 227320 - Motion Blur on Transform node freezes Nuke on high process thread machines

Using a computer with a high thread count causes the motion blur on non-GPU nodes to make Nuke unresponsive temporarily while it buffers. The more frames being processed and the more threads in use seems to effect the length of the freeze.

 

It occurs to a lesser extent in Nuke 9, but the pause is dramatically more noticeable in Nuke 10.

 

With the same machine but on CentOS 6.7, the problem did not occur and the playback was very fast.

 

Nuke 10.0v3 - Windows 10

 

With a high theaded machine:

1) Read in a sequence of frames

2) Add a Transform node

3) Increase the Motion Blur value in the properties

4) Play the sequence

5) It will freeze while buffering

6) Load Nuke with -m 1 flag to limit the threads

7) Repeat steps, no freeze

8) Load with -m 16

9) Still freezes but for not as long

 

With Dual 18-core Xeon E5-2699 v3 (2.30 GHz):

 

To buffer the Transform Motion Blur without freezing Nuke

 

Nuke becomes unresponsive while it buffers the Motion Blur