A modern programming language that makes developers happier.

kotlinlang

Why is the last `log` showing a `DefaultExecutor` context and not `SINGLE-THREAD`?

It is definitely a bug. Can you, please, file it. Looks like we broke something in `withContext` in one of the recent updates.

(very bad that it was not caught by tests)

<@U2E974ELT> can't it be the compiler mixing/messing the two coroutines we have here?

<@U2E974ELT> Thought I was going crazy. Will file it. This seems to be causing a hang in my program. What is my best workaround?

FYI: <https://github.com/Kotlin/kotlinx.coroutines/issues/431>

Phew… not a bug.. figured it out. I’ll write in the issue

Looks like the context is correct, but the Thread isn't.

You shutdown the executor too early (with `use`). It cannot execute anymore, so default executor is used.

So you can remove the `bug` tag <@U2E974ELT> :wink:

Ah, because `launch` returns before it completes. That makes sense.

<@U2E974ELT> The solution of moving `join` up works for the example I gave, but in my actual app, the `newSingleThreadContext` is instantiated from non-coroutine code, which needs to be call this code and continue. Therefore I can't join the `launch`. I guess I could always start a Thread that does nothing but do the `launch` + `join` (or `runBlocking` really), but that seems really messy as now I have a useless thread hanging around. What am I missing?

<@U0NT624JZ> You can just not use the `.use` extension

As long as nothing stops the thread, you are free to use it

Does it make sense to default to the DefaultExecutor instead of throwing?

Yes. It does. It would usually happen when coroutine is shutting down, too, and is in the processing of executing its `finally` sections, releasing resources it had acquired. We should run those. That gives us a chance to be able to recover.