Problem summary
Nuke crashes when loading a specific quicktime .mov file on a CPU using full threads with a 32 thread count or higher machine.
Nuke Studio/Hiero does not crash when ingesting the file on the timeline, but will crash when reading the file in from the Node Graph.
Customer reported version
Nuke 15.0v1
Customer reported platform
RHEL 9
Steps to reproduce
1) Download the attached .mov file.
2) Launch Nuke then import the downloaded .mov file.
3) Observe performance in Nuke. If it doesn't crash, Read in the file again.
Expected behavior
Nuke should load the file and remain stable.
Actual behavior
Nuke will crash when reading in the specific .mov quicktime file. Sometimes the .mov file needs to be imported a second or third time before the crash occurs, usually after clearing Nuke's cache before initially loading the file.
It has also been seen that Nuke will crash when viewing the Preview window of the File Browser when selecting the file before loading it.
Workaround
Launching Nuke with limited threads using the
-m flag allows the .mov files to read without crashing the software. This has been tested by reducing the thread count for the CPU by at least 1 on a 32 thread machine by using the command
-m 31, where the crash was occurring previously when using all threads. Additional thread reduction was required in a machine with a larger thread count (48), where reducing it to 24 helped.
Reproduced by Support in:
Nuke 15.0v4 - Windows 10, Windows 11
Nuke 14.1v4 - Windows 10/11, CentOS 7
Nuke 12.2v1 - Windows 10/11, CentOS 7 -
regression
Unable to reproduce bug in:
Nuke 15.0v4 - Windows 10, Rocky 9 (16 thread CPU)
Nuke 14.1v4 - CentOS 7 (16 thread CPU)
Nuke 12.1v5 - Windows 10/11, CentOS 7 (32 thread CPU)
Earliest version tested
Nuke 12.1v5 - This issue doesn't appear in this version and has regressed