Was the KN memory model changed again in 1.5? I’m getting a lot of freeze errors on iOS after updati...

# multiplatform

[Mike]

Was the KN memory model changed again in 1.5? I’m getting a lot of freeze errors on iOS after updating. Spent all afternoon debugging it.

[Thomas]

Maybe you are running into this issue? https://github.com/Kotlin/kotlinx.coroutines/issues/2688

[Mike]

I’m using reaktive (rx library) in my multiplatform project and not coroutines, I’ll check if it might be related

[Arkadii Ivanov]

The memory is not changing, but it may start freezing things in some new conditions (possibly due to bug fixes etc.). There are two ways to deal with freezing: either make the related code freezable (atomics, etc.), or prevent the freezing. To find the freezer you can use ensureNeverFrozen on the object being frozen. It will produce a readable stack trace pointing to the freezing site.

[Mike]

I’m planning to pare down the issue when I find some time. It seems to affect most of my network calls. The GitHub coroutines thread around timeout is somewhere I might start first, since I use timeout operator in my network calls that’s throwing the immutable error (though I’m not using coroutines)

[Arkadii Ivanov]

If you are talking about Reaktive timeout operators, then it should not be related to the pinned issue. Try adding ensureNeverFrozen to the object being frozen, you will find the cause.

[Mike]

Btw, it looks like the issue I saw was due to a kotlin serialization bug: https://github.com/Kotlin/kotlinx.serialization/issues/1450

[Arkadii Ivanov]

Thabks for letting me know!