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

Use supervisor to manage condition variables #5

Closed
jvoegele opened this issue Aug 31, 2017 · 1 comment
Closed

Use supervisor to manage condition variables #5

jvoegele opened this issue Aug 31, 2017 · 1 comment

Comments

@jvoegele
Copy link
Owner

Currently, condition variables are implemented as an unsupervised GenServer process that is lazily initialized on first use, whether that is in the signal macro or as a :signal option in one of the wait* macros. Furthermore, the condition variable process is linked to the process that first used it and if this process exits it will also cause the condition variable process to exit even if other processes are still relying on it.

To fix this issue, condition variables should be started by and linked to a supervisor process instead of the (arbitrary) first process that happens to use the condition variable.

@jvoegele
Copy link
Owner Author

jvoegele commented Sep 2, 2017

Resolved by Pull Request #7

@jvoegele jvoegele closed this as completed Sep 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant