ID 468076 - Using Nuke Studio with Monitor Out enabled for extended periods causes tearing/artefacts in the Timeline Viewer and Monitor Out Viewer

Problem summary

Using Nuke Studio with Monitor Out enabled for extended periods causes tearing/artefacts in the Timeline Viewer and Monitor Out Viewer

Once Nuke Studio is in the state where is starts artifacting:

• Only re-launching Nuke Studio seems to stop it for a time
• Mousing over the Viewer causes that frame to redrawn correctly, but next time you change frame the artefact can come back
• Disabling Monitor out prevents it, but re-enabling it causes the issue to come back
• Changing between different Monitor Out devices (Floating Window and Kona 5) made no difference
• Opening new sequence viewers made no difference
• It only seems to affect the Timeline Viewer, not the Node graph Viewer
• Clearing Playback cache doesn't help
• Making a new sequence, the issue continues
• Closing the project completely and making a new project in the same session with different footage, the issue continues
• The artefact is random every time to reload the frame

Customer reported version
nuke.12.2v4

Customer reported platform
centos7

Steps to reproduce

1) Open Nuke Studio

2) Enable Monitor out using Floating Window or a dedicated Monitor Out device (Kona 5 was tested with)

3) Import footage, perform edits, soft effects, create comps, playback and do this for multiple sequences

4) Keep working in Nuke Studio for 2-4 hours, eventually, when stepping between frames you get tearing artefacts

Note, just having Nuke Studio open for extended periods of time does not cause the issue, lots of edits need to be made. A timelapse of encountering the issue is below, along with the random frames test footage to easily see if the issue has been encountered.
 

Expected behaviour

For the Viewers to show the correct images

Actual behaviour
The viewer shows random artifacts when stepping through frames, or when playing back:

​

​Also happens with new projects within the same Nuke Studio session:

​

Workaround

Closing and re-opening Nuke Studio fixes the issue for a while

Reproduced by support
This bug has been reproduced in:

Nuke Studio 12.2v5 - centOS 7.7

Nuke Studio 12.2v3 - centOS 7.7

Unable to reproduce bug in:
Nuke Studio 12.2v5 - Windows 10

Earliest version tested
Nuke Studio 12.2v3 - Did not test further back due to nature of how long the tests take