ID 518041 - Timeline Viewer renders black outside the in and out points if you make edits to a track like disable and re-enabling it, or moving clips

Problem summary
Timeline Viewer renders black outside the in and out points if you make edits to a track like disable and re-enabling it, or moving clips
 
This seems to be worse with longer projects, loaded from the network
 
Customer reported version
nuke.13.2v3
 
Customer reported platform
n_a_linux
 
Steps to reproduce
 
1) Open Nuke Studio and load the project: \netshare\support\tickets\slowProject\SlowProject_v001_NS13.2v3.hrox
 
2) Move the playhead to 01:06:00:00

3) Click the timeline and press U, to set the in/out points to the current clip

4) With the playhead in the in/out range, disable and re-enable the top track, the Viewer renders the bottom track, then back to the top track
 
5) Move the playhead outside the in/out range, disable and re-enable the top track, the Viewer renders the bottom track, then renders black
 
If you scrub the timeline, sometimes the viewer will start to render again, but toggling the top track, or moving clips on the timeline brings the issue back.
 

 
Expected behaviour
For the viewer to render the image after a change has been made to the sequence
 
Actual behaviour
The viewer renders black
 
Workaround
Temporary Workaround: If you scrub the timeline between the in/out points, then the viewer will start rendering outside the in/out points again, until you make another change to the sequence:
 

 
Reproduced by support
This bug has been reproduced in:
Nuke Studio 13.2v3 - Windows 10, CentOS 7, macOS Monterey
Nuke Studio 13.2v2 - Windows 10, CentOS 7, macOS Monterey - Regression in 13.2 line
Nuke Studio 13.1v4 - Windows 10 - Regression in 13.1 line
Nuke Studio 13.0v8 - Windows 10 - Regression in 13.0 line
 
Unable to reproduce bug in:
Nuke Studio 13.2v1 - Windows 10, CentOS 7, macOS Monterey
Nuke Studio 13.1v3 - Windows 10
Nuke Studio 13.0v7 - Windows 10
Nuke Studio 12.2v11 - Windows 10
 
Earliest version tested
Nuke Studio 12.2v11 - This issue doesn't appear in this version and has regressed