Now in rare conditions line 6 is being executed af...

# coroutines

[Paul Woitaschek]

Now in rare conditions line 6 is being executed after I cancelled the job.

[Vsevolod Tolstopyatov [JB]]

yes, because you can invoke cancel after render method started its execution

[Paul Woitaschek]

How is that possible?

[Vsevolod Tolstopyatov [JB]]

you can boil your example down to:

// Thread 1
if (flag) {
   render()
}

// Thread 2
flag = false

[Vsevolod Tolstopyatov [JB]]

do you expect render to be invoked when both threads are running concurrently?

[Paul Woitaschek]

But what is thread 2?

[Vsevolod Tolstopyatov [JB]]

oops, I’ve missed the fact that cancellation is run from the main thread

[Paul Woitaschek]

consumeEach is executed on the main thread, right? So how can I cancel it on the main thread if the main thread is running?

[Vsevolod Tolstopyatov [JB]]

is render a suspend function?

[Paul Woitaschek]

No

[Paul Woitaschek]

I can catch the case and send silent crashes to my crash reporting tool.

[Paul Woitaschek]

What should I log to debug this issue?

[Vsevolod Tolstopyatov [JB]]

what does get do?

[Vsevolod Tolstopyatov [JB]]

is viewModel a CoroutineScope? Are you cancelling job or viewModel?

[Paul Woitaschek]

viewModel is no CoroutineScope

[Paul Woitaschek]

fun CoroutineScope.get(billingModule: BillingModule, skuDetailSelected: ReceiveChannel<SkuDetail>): ReceiveChannel<VideoPromoState> {

[tateisu]

You can check coroutineContext [Job] ?. isActive before, after, and inside render ().

[Paul Woitaschek]

I can but I shouldn't have to

[Paul Woitaschek]

btw this has moved to a private conversation as I shared confidential code