You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Currently, condition variables are implemented as an unsupervised
GenServer
process that is lazily initialized on first use, whether that is in thesignal
macro or as a:signal
option in one of thewait*
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.
The text was updated successfully, but these errors were encountered: