Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Fix spec of Thread#status for an externally killed thread that sleeps #4815
There could be a race here, if a thread marks itself as aborting and then some other thread tries to exit sleep at the same time, but ideally exitSleep should only be called by that thread when it transitions. The uses I reviewed seem to fit that pattern.
Worst case, some bad actor might cause an aborting thread to mark itself as runnable again. it would be no worse than now but less likely to happen.
Oct 12, 2017
1 check failed
FWIW The way we do in in TruffleRuby is to save/restore the Thread status around sleep/blocking tasks.