On Mon Jan 15 13:04:02 2024 +0000, Rémi Bernon wrote:
Fwiw I believe I saw cases of unix_tid being -1 and causing setpriority errors being printed. I didn't really investigate, so not sure exactly how it happens but probably worth having a better look.
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).