Problem summary
Nuke freezes when a Tracker node has upstream localised footage, and has a node expression linked to it, displaying it's Curve Editor
This only happens for the output transforms knobs from the Tracker node, and the localised Read node doesn't actually need to be localised footage.
The longer the footage, the longer Nuke freezes.
Customer reported version
nuke.15.0v1
Customer reported platform
rocky9
Steps to reproduce
1) Create an empty Read node, setting the file knob to test_####.exr, the last frame knob to 1000 and set the localisation policy to on.
2) Connect a Tracker node
3) Create any node, like a Grade node, and expression link any knob to the Tracker node's Transform translate knob
4) Open the Curve Editor, making sure the Grade node's Properties are open, and try to do anything in the Node Graph, Nuke freezes constantly.
5) In the Read node set the last frame knob to 10000, Nuke will now freeze for even longer
Expected behaviour
To be able to create nodes and edit knobs values without issue:
Actual behaviour
Nuke freezes constantly, making it practically unusable:
Workaround
None
Reproduced by support
This bug has been reproduced in:
Nuke 15.0v1 - Windows 10, Rocky 9.2, macOS Monterey
Nuke 14.0v4 - Windows 10, CentOS 7.9, macOS Monterey - regression
Unable to reproduce bug in:
Nuke 14.0v3 - Windows 10, CentOS 7.9, macOS Monterey
Earliest version tested
Nuke 14.0v3 - This issue doesn't appear in this version and has regressed