now that this is fixed: <https://youtrack.jetbrain...

# ktor

[Kris Wong]

now that this is fixed: https://youtrack.jetbrains.com/issue/KTOR-973, I am getting this instead: kotlin.native.concurrent.FreezingException

[Kris Wong]

Untitled

Untitled

[Kris Wong]

@basher any thoughts on whether could be related to mixing CoroutineWorker with the latest native-mt coroutines in Ktor?

[Kris Wong]

i have not had a chance to go back and update where I was using CoroutineWorker originally

[basher]

Unsure. If you're using native-mt, you shouldn't really need/use CoroutineWorker

[basher]

Would need to see some code though

[Kris Wong]

yeah that's difficult. should be a simple matter to swap in coroutines though

[basher]

CoroutineWorker is only meant to help while multi-threaded coroutines aren't officially supported in the main release. I haven't spent much time with native-mt, so I'm not sure what changes might be needed to make CoroutineWorker play well with it

[Kris Wong]

understood

[e5l]

Hey, @Kris Wong. Could you tell me why do you need CoroutineWorker with native-mt coroutines?

[e5l]

You can launch on newSingleThreadContext() and it will give you dispatcher on the separate worker

[Kris Wong]

@e5l because migrating away from coroutineworker takes an investment in time that i haven't made yet

[Kris Wong]

though at this point my plan is to migrate away from Ktor, because this module needs to be used in production soon