Problem summary
Nuke/Nuke Studio's QuickTimeHelper-32.exe process delays QuickTime Player's boot by 30 - 80 seconds when Nuke is running on a Windows OS.
Customer reported version
nuke.n/a
Customer reported platform
Windows 10
Steps to reproduce
1) Open QuickTime Player (v7.7.9) on Windows 10 and note that it boots within a few seconds.
2) Close QuickTime Player and open a script in Nuke 11.1v2, then boot QuickTime Player again.
3) Note that it takes about 30 - 80 seconds for QuickTime Player to open, depending on the complexity of the script.
4) Close QuickTime Player and open Windows Task Manager. In the Processes tab, highlight the QuickTimeHelper-32.exe's and end each process.
5) With Nuke still running, relaunch QuickTime Player, and note that it now boots within a few seconds.
Workaround
None.
Reproduced by support
Nuke 11.1v2 - Windows 7
Nuke Studio 11.1v1 - Windows 7
Nuke 11.0v4 - Windows 7
Nuke 11.0v1 - Windows 7
Nuke 10.5v7 - Windows 10
Nuke 10.5v1 - Windows 10
Nuke 10.0v6 - Windows 7
Nuke 10.0v1 - Windows 7
Nuke 9.0v9 - Windows 7
Nuke 9.0v1 - Windows 7
Unable to reproduce bug in:
This did not reproduce on macOS 10.11 on any Nuke version, with QuickTime Player v10.4.
This is N/A for Linux, as it does not have an official QuickTime Player version.
Nuke 8.0v7 - Windows 7
Nuke 8.0v1 - Windows 7
Nuke 7.0v10 - Windows 7
Earliest version tested
Nuke 7.0v10
Expected behaviour
QuickTime should launch immediately without the QuickTimeHelper-32.exe process hindering it
Actual behaviour
QuickTime Player takes at least 30 seconds to launch if Nuke 9.0v1 or beyond is open, as at least 1 instance of the QuickTimeHelper-32.exe process is launched with it. If a script is open in Nuke, it may take longer for QuickTime Player to open, depending on the number and type of nodes present in the script. Reducing the number of Nuke's QuickTime decoders (Edit > Preferences > Threads/Processes) from 8 decoders to 1 decoder still causes the same delay in QuickTime Player's launch.