confusingly, that same exception will be thrown when k/n expects something to be frozen and it's not
Kris Wong
05/04/2020, 6:37 PM
if that's not the issue then it may be a bug
h
Hauke Radtki
05/04/2020, 6:38 PM
True, and as far as I understand it's throwing this exception while setting the (optional) owner parameter, so that seems like a bug to me
Hauke Radtki
05/04/2020, 6:38 PM
Copy code
at kfun:kotlinx.coroutines.sync.MutexImpl.LockedQueue.<set-owner>#internal (0000000000589100)
at kfun:kotlinx.coroutines.sync.MutexImpl.unlock(kotlin.Any?) (00000000005875a0)
Hauke Radtki
05/04/2020, 6:39 PM
But also might be hiding another problem, or a missunderstanding how Kotlin/Native Mutexes should be used