Something weird happening here, I launch a coroutine on a single thread context and the profiler sho...

# coroutines

[coder82]

Something weird happening here, I launch a coroutine on a single thread context and the profiler shows me it creates a thread, runs the coroutine and puts that thread in WAIT, so my app is leaking threads?

[coder82]

but I suspect here is the culprit

[coder82]

override val coroutineContext:CoroutineContext
    get() = Executors.newSingleThreadExecutor().asCoroutineDispatcher()

[coder82]

every time i use coroutineContext

[coder82]

it creates a new one? -_-

[coder82]

override fun invokeLater(vararg params:Any, block:suspend AdapterProcess.() -> Unit):Job {
    currentJob = launch(coroutineContext) {
        [e-mail]()
    }
    return currentJob
}

[coder82]

it must definitely be what is going on, what do you reckon?

[mateusz.kwiecinski]

each time you access coroutineContext field you invoke getter get() hence you create new singleThreadExecutor on each invocation.

override val coroutineContext:CoroutineContext = Executors.newSingleThreadExecutor().asCoroutineDispatcher()

☝️ this would assign created dispatcher to a field once and read its value later

[coder82]

yes indeed now the profiler shows me always the same thread

[coder82]

crazy... this has been lurking in my code since forever

[coder82]

problem solved, when I wrote that line I must have been drunk, really.