anyway, I think this happens, because my threads continue to run even after everything else was released.
So yeah, that's not great, but also shouldn't cause any issues. What I think is causing issues is mostly just how things run at application exit and sometimes the order could mess things up?
Not quite sure :) Maybe it's just LLVM trashing the memory, but I'm also too lazy to dig why exactly this happens.
Anyway, I should terminate my threads early regardless.
@karolherbst I love those! Somehow I seem to attract this bug in particular, and the result is always something silly (like memory-pool/GC quirks, or integers being cast between 64 and 32 bit at a bad spot).
Only once was it a compiler error ^^