Does anyone have any experience with multithreadin...
# kotlin-natives
Sam Schilling
09/26/2019, 4:55 PMDoes anyone have any experience with multithreading on macOS and getting around all the IllegalStateExceptions? I am seeing lots of random crashes but that seems somewhat expected because I am using
TransferMode.UNSAFEb
basher
09/26/2019, 4:57 PMI haven't heard anyone dive into the full implications of using
TransferMode.UNSAFEs
Sam Schilling
09/26/2019, 4:58 PMYeah, I had to though because
TransferMode.SAFEexecutes
Sam
09/26/2019, 4:59 PMYou need to freeze your objects before passing them to workers.
s
Sam Schilling
09/26/2019, 4:59 PMPerhaps I need to switch to safe transfer, but it seems like that doesn’t support modifying any data that is transferred or sharing across threads
Sam Schilling
09/26/2019, 4:59 PMI’ve tried that (freezing) in the past many times and in many ways with the same exceptions but I can try digging into that again
b
basher
09/26/2019, 5:11 PMFreezing is the simplest, but it does mean you can't do the kind of sharing it seems you want to do
s
Sam Schilling
09/26/2019, 5:12 PMYeah, the shared XOR mutable restriction, while understandable for safety, is really biting me
b
basher
09/26/2019, 5:12 PMthere are strategies like using AtomicReference and other Atomic* classes for shared references/data across threads
s
Sam Schilling
09/26/2019, 5:17 PMIt would be great if coroutines supported multithreading on background threads 😞
b
basher
09/26/2019, 5:26 PMbasher
09/26/2019, 5:27 PM@louiscad just added macOS support too 🙂
👋 1
k
kpgalligan
09/26/2019, 5:35 PMI’ve delved into the implications of UNSAFE. You absolutely should never use it if you can’t explain what the problem with using it is, and even then, basically don’t. In summary, reference counting is not atomic on thread confined state, so you get crashes because objects are deallocated but the runtime thinks they’re alive.
🎉 1
kpgalligan
09/26/2019, 5:36 PM6 Views