On Mon Jan 15 14:24:07 2024 +0000, Marc-Aurel Zent wrote:
I think this can happen when the thread gets killed by the looks of it (or alternatively `get_unix_tid()` returned -1, but in that case I don't see how it could fix itself later).
Should be guarded against now, `set_thread_affinity()` has a similar check