f27baa71e4
The thread state management used by the GC and the liveliness monitoring lazily creates entries for application threads that call (certain) Cyclone API functions. It arranges for the entry allocated to such a thread to be cleared once the thread terminates. This means that if such a thread still exists once the last participant is deleted (and Cyclone deinitializes), the corresponding thread entry still exists as well. The assertion that all (known) threads must have stopped on shutting down Cyclone is therefore incorrect. This commit introduces a special state for thread entries that were created lazily. It does monitor that they do not stay in the "awake" state for too long, but otherwise doesn't care much about them. Signed-off-by: Erik Boasson <eb@ilities.com> |
||
|---|---|---|
| .. | ||
| ddsc | ||
| ddsi | ||
| xtests | ||
| CMakeLists.txt | ||