Under what circumstances would `delay` suspend forever, if I pass it a value around 500-1500 MS? I h...

# coroutines

[Dico]

Under what circumstances would delay suspend forever, if I pass it a value around 500-1500 MS?
I have some code that is looping with an interval which works perfectly in one environment but not in another - where it's used as a plugin in some other software.
The dispatcher used is a single thread dispatcher created using Executors.newSingleThreadDispatcher(threadFactory).asCoroutineDispatcher()
The behavior I'm seeing is that it never resumes the coroutine.

[gildor]

It may be deadlock

[gildor]

Especially with single thread dispatcher

[gildor]

If some code blocks coroutine, delay also cannot be dispatched and will never return

[gildor]

Do you have some use case for single threaded dispatcher?

[Dico]

avoiding shared mutable state

[Dico]

I think it's probably blocking somewhere as well

[Dico]

thanks for the responses

[gildor]

avoiding shared mutable state

I would use actor for this

[gildor]

in general limiting coroutine concurrency using threads is not really good idea (often it cause unexpected behavior, when you think that suspending will not allow other coroutines to run because you are on single threaded dispatcher), better to use actor, which is 1 coroutine that process queue of events

[Dico]

I'm conscious that an actor is good for this, but it's not needed. You can actually use LimitingDispatcher atm with a bit of experimental trickery by the way, which is pretty cool.

[Dico]

Turns out the parent Job was getting cancelled immediately due to a big oversight

[Dico]

😅