Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Termination of Multipleprocessing/Pool #64

Open
TCC-dev opened this issue Mar 18, 2022 · 0 comments
Open

Termination of Multipleprocessing/Pool #64

TCC-dev opened this issue Mar 18, 2022 · 0 comments

Comments

@TCC-dev
Copy link

TCC-dev commented Mar 18, 2022

The multiple processing tasks do not seem to terminate themselves right away if the parental node is interrupted. If each process has an end then the process will be ended at the end eventually. But if a process falls in an infinite loop or becomes halted, the process will stay in the background even after the parental node is refreshed or the GPI is closed. Is it possible to have the mulitple processing framework to be controlled by the parental GPI node when interruption occurs?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@TCC-dev