ID 527773 - The Cryptomatte node crashes Nuke when an EXR with specific metadata is upstream

Problem summary:

The Cryptomatte node crashes Nuke when an EXR with specific metadata is upstream.

Customer reported version:

Nuke 13.1v3

Customer reported platform:

CentOS 7

Steps to reproduce:

1) Download the attached file: test_render_003.exr

2) Create a Read node, and read in the downloaded test_render_003.exr file

3) Create a Cryptomatte node and connect it to the Read node, Nuke should crash.

Expected behavior:

Nuke should not crash when connecting a Cryptomatte node to an EXR with specific metadata.

Actual behavior:

Nuke crashes if an .EXR file contains specific metadata. In this case, the metada for exr/glimpse.settings.cryptomatte.numRanksInternal and exr/glimpse.settings.cryptomatte.numRanksOutput.

Workaround:

Using the metadata TCL command in the ModifyMetaData node to re-add the same values:

ModifyMetaData { metadata {   {set exr/glimpse.settings.cryptomatte.numRanksInternal "\[metadata exr/glimpse.settings.cryptomatte.numRanksInternal]"}   {set exr/glimpse.settings.cryptomatte.numRanksOutput "\[metadata exr/glimpse.settings.cryptomatte.numRanksOutput]"} } }

Reproduced by Support in:

Nuke 14.0v1 - Windows 10, Windows 11, CentOS 7

Nuke 13.1v3 - Windows 10

Nuke 13.0v1 - Windows 10, CentOS 7

Earliest version tested

Nuke 13.0v1 - The native Cryptomatte feature did not exist before this version