It is comfirmed with our test, that when Ctrl-C is input in the initialization phase of cgfNodes, the driveworks context cannot be released properly, thus no output the process_log with Releasing Driveworks SDK Context, and finally cause the cgf reboot issue(resource temporily unavailable).
In contrast, when Ctrl-C is input during the schedule phase of cgfNodes, the driveworks context can be released correctly, thus you can see the process_log with Releasing Driveworks SDK Context. And you can relaunch the cgf_app without any issue.
- Could you help to figure/explain the behavior handling
Ctrl-C? - Please promote this issue resolution!