When launching Nuke through AYON/OpenPype under Centos 7 or Rocky 9 (maybe more), when Nuke exitsm zombie process remains. This especially sucks on render farm machines where it can quickly become huge problem.
We've encountered it before and we thought that it is caused by process forking in Python, so we introduced C code that can be compiled and used instead of Python version app_launcher - the code is here:
Although it seemed at the time it solved the problem, it was never confirmed. Now it seems that it is happening somewhere else (or that it is different problem altogether).
When Nuke is launched via AYON/OP and our menu.py execution is inhibited (so the AYON integration isn't present), no zombie processes are created. This suggest that it isn't directly related to forking issue.
How to replicate the issue?
No response
Additional context:
()
(might be a private channel)
This issue was automatically created from Clickup ticket AY-6170
Please describe the issue you have encountered?
When launching Nuke through AYON/OpenPype under Centos 7 or Rocky 9 (maybe more), when Nuke exitsm zombie process remains. This especially sucks on render farm machines where it can quickly become huge problem.
We've encountered it before and we thought that it is caused by process forking in Python, so we introduced C code that can be compiled and used instead of Python version app_launcher - the code is here: Although it seemed at the time it solved the problem, it was never confirmed. Now it seems that it is happening somewhere else (or that it is different problem altogether).
When Nuke is launched via AYON/OP and our menu.py execution is inhibited (so the AYON integration isn't present), no zombie processes are created. This suggest that it isn't directly related to forking issue.
How to replicate the issue?
No response
Additional context:
() (might be a private channel)
This issue was automatically created from Clickup ticket AY-6170