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.

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

Threads/processes not terminated in some states when fork-on-schedule #8

Open
stefanbucur opened this issue Sep 11, 2013 · 0 comments
Labels

Comments

@stefanbucur
Copy link

Reported by Paul Thompson

Executor.cpp (executeThreadExit)

3217 thrIt->second.enabled = false;
3218
3219 if (!schedule(state, false))
3220 return;
3221
3222 state.terminateThread(thrIt);

If fork-on-schedule is true, schedule may create other states. In this case, the thread will only be terminated in one of the states and will remain disabled in the others. At least, I think this is what could happen. A similar situation occurs in executeProcessExit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant