ID 553284 - Terminal hangs when attempting to batch render a scene that errors due to an imageRead node pointing to a non existing file.

Problem summary
Terminal hangs when attempting to batch render a scene that errors due to an imageRead node pointing to a non existing file.
 
Customer reported version
Katana 4.5v6
 
Customer reported platform
CentOS7
 
Steps to reproduce
1) Download the attached image_read_hang.katana file and copy either of the following scripts based on your OS to start the batch render.

 

Windows: 

katanaBin.exe --batch --render-node comp --katana-file path\to\image_read_hang.katana -t 1

Linux: 

katana --batch --render-node comp --katana-file path/to/image_read_hang.katana -t 1

 
2) Open a terminal and use the cd command to navigate to your Katana installation.
 
3) Run the script you copied and modified the scene path.
 
4) Observe the batch render fail and the inability to execute further commands in the terminal.
 
Expected behaviour
The batch render fails with an exit code, then allows the user to input new commands into the terminal.
 
Actual behaviour
After failing, the terminal locks up and does not allow any new commands to be executed.
 
Workaround
In the "Project Settings" tab, change compDefaults.fileIn.missingFrames to "Black". This will override the error and instead render a black image.
 
Reproduced by support
Katana 4.5v5 Windows | CentOS7
Katana 4.5v6 Windows | CentOS7
Katana 6.0v1 Windows | CentOS7 (in CentOS a segmentation fault occurs)
Katana 6.0v2 Windows | CentOS7 (in CentOS a segmentation fault occurs)
Katana 6.0v3 Windows | CentOS7 (in CentOS a segmentation fault occurs)
 
Unable to reproduce bug in:
Katana 4.0v4 Windows | CentOS7
 
Earliest version tested
Katana 4.0v4 - This issue doesn't appear in this version and has regressed