Starting `freeze()` issue thread. Continued from here: <https://kotlinlang.slack.com/archives/C3PQML...

# multiplatform

[kpgalligan]

Starting freeze() issue thread. Continued from here: https://kotlinlang.slack.com/archives/C3PQML5NU/p1567102026052800 cc @Kris Wong @basher

[Kris Wong]

thanks

[kpgalligan]

Thread is so we don’t sort out something interesting in private.

[Kris Wong]

man, app code gets real confused when I right click in the editor

[Kris Wong]

er, i don't even see how to run in tests in this thing

[kpgalligan]

In app code?

[Kris Wong]

yeah

[kpgalligan]

I don’t know. I would just log before/after freeze and first confirm it is stopping there. The debugger may be tricky to set up for app code tests

[Kris Wong]

that's definitely were it stopped when running in Xcode

[Kris Wong]

let me try just running the app

[kpgalligan]

How do you know if the debugger isn’t working?

[Kris Wong]

i know it stopped there, I just can't step into the call to see where it stopped underneath that call

[kpgalligan]

This is just freeze or it’s doing a bunch of threading stuff?

[Kris Wong]

just freeze

[kpgalligan]

You’re saying if I create an Xcode project and just call freeze on a kotlin object you’d expect it to deadlock?

[kpgalligan]

In a test

[Kris Wong]

well, the project is much complex than that, but that's essentially what happening

[kpgalligan]

I guess I need to see that or I would assume something else is happening.

[Kris Wong]

yeah I am trying to investigate but things are moving very slowly

[kpgalligan]

I mean, I’ve had some strange issues with KN, but freeze deadlocking would indeed be a surprise

[kpgalligan]

Freeze itself happens before you’ve shared code with other threads, so in theory it’s not locking on anything. If execution simply stops there, and you’re 100% sure it isn’t a crash or involved in some other form of infinite loop, it would be very interesting to see that in action.

[Kris Wong]

wow, this is pretty spectacular

[Kris Wong]

if you have this actual fun <T> T.freeze(): T = this.freeze()...

[Kris Wong]

it's very important you also have this import kotlin.native.concurrent.freeze

[basher]

ah nice

[basher]

problem solved haha

[Kris Wong]

because it builds w/o that, and then it's just an infinite loop

[Kris Wong]

that was a fun exercise. thanks fellas.

[kpgalligan]

I have done this

[Kris Wong]

it's pretty easy to figure out when you can actually see the stack trace

[Arkadii Ivanov]

You can use 'by' to import KN's freeze as e.g. 'freezeNative', then call it. It will be much less error prone.