Problem summary
Script that consists of a CameraTracker node, with a mask input and 4K footage, causes Nuke to become unresponsive
Customer reported version
nuke.10.0v3
Customer reported platform
windows10
Steps to reproduce
steps to repro:
1. open Nuke
2. Read in customer script
3 Replace read node with own 4K footage. I used:
Q:/Testing/Nuke/FileIO/dpx/Attenborough_dpx_INT/ATLANTIC_FM_MAIN_SHOW_01_to_foundry_right/to_foundry_right.#####.dpx
4. Open the properties of the CameraTracker > Track and Solve footage
5. Continue switching selecting nodes
6. Create new nodes (a bunch of grades, color corrects, merges, blurs etc)
7. Switch back to selecting the CameraTarcker node
Result: every so often Nuke will become non responsive
tried to recreate the non responsiveness with my own script, but was unable to do so.
1. open nuke
2. read in:
Q:/Testing/Nuke/FileIO/dpx/Attenborough_dpx_INT/ATLANTIC_FM_MAIN_SHOW_01_to_foundry_right/to_foundry_right.#####.dpx
3. Create a camera tracker node and match it settings to the customers
4. create a Roto node and a roto shape
5. attach it as a mask to the camera tracker node
6. Open the properties of the CameraTracker > Track and Solve footage
7. Continue switching selecting nodes
8. Create new nodes (a bunch of grades, color corrects, merges, blurs etc)
9. Switch back to selecting the CameraTarcker node
Result: no non responsiveness
Workaround
rebuild script
Reproduced by support
Reproduced on Windows8 Nuke10.0v4, 9.0v8, 8.0v6
Could not repro on OSX 10.11.3 Nuke10.0v4
Expected behaviour
Nuke to not become unresponsive
Actual behaviour
Nuke becomes intermittently unresponsive