Hi Daniel: This is a shot in the dark without seeing your actual script but the behavior matches something I've seen before. Do you have expressions/python code that execute anytime there is an update to the tree? You may need to check your script editor to see this. If there is code being executed every time there is an update to the tree any where that will also explain why it gets worse as the tree gets bigger (more nodes = more code to chew through) And as far as I know, that coded is being processed by one proc.
I put a request for Foundry to look at this a while back: Bug 35703 - Expressions evaluated in unrelated parts of tree Development gave the following details in response: "...this is a known bug. The root cause is the way Nuke handles expression links between knobs. There is currently no way of knowing if changes in any part of a script will affect the result of a particular expression without evaluating that expression." In the past to get around this, I've copied over the roto node to an empty script only to copy it back after I've made my edits. Elvis ----- Original Message ----- From: "Daniel Hartlehnert" <[email protected]> To: "Nuke user discussion" <[email protected]> Sent: Friday, March 4, 2016 11:00:16 AM Subject: [Nuke-users] Nuke locking up with 1 cpu busy Hi, sorry for cross-posting this from the forums, but i hardly got any response there. I tend to get this behavior in Nuke quite often with bigger scripts and it just gets unusable. The symptom is Nuke completely locking up when dbl-clicking a node to open its properties. Usually it happens when dbl-clicking a roto or rotopaint node. Looking in the system monitor, i can see that 1 (out of 12) cpu’s is 100% busy, and maybe, if you wait long enough, it will eventually be ok. But i have waited for several minutes sometimes, still no go. So the only option is to force quit out of Nuke. The odd thing is, i can sometimes work in the same script for hours, then suddenly the symptons start to show up. I even had it affect other nodes as well. So dbl-clicking a merge node for example too ages. I am on Nuke 8.0v6 on Linux. So my question is: are there any operations in Nuke that are single threaded esp. regarding Rotos that could trigger this behavior? Have other people seen this as well? Regards, Daniel_______________________________________________ Nuke-users mailing list [email protected], https://urldefense.proofpoint.com/v2/url?u=http-3A__forums.thefoundry.co.uk_&d=CwIFaQ&c=hHkK43hKb5uKUGaYMJ-p252cFdfVBHtyegDvswk59fU&r=ilRVisJEHQmq9__Xya9HaQsNGSKiRcQWFhzTKtLfVGE&m=xwcgBNYY4WZEQKkwg6glCgaJgv8rIYpAIVFYKItVAy8&s=J36lFYVResxadI3h1dkBqxJPG3pj9G1mENp3es6CKCA&e= https://urldefense.proofpoint.com/v2/url?u=http-3A__support.thefoundry.co.uk_cgi-2Dbin_mailman_listinfo_nuke-2Dusers&d=CwIFaQ&c=hHkK43hKb5uKUGaYMJ-p252cFdfVBHtyegDvswk59fU&r=ilRVisJEHQmq9__Xya9HaQsNGSKiRcQWFhzTKtLfVGE&m=xwcgBNYY4WZEQKkwg6glCgaJgv8rIYpAIVFYKItVAy8&s=GQr-0hea83arFuOwsdNB3_x8LEiHprW51yRZlmY0HMk&e= _______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
