Can I debug it further, I don't see where could a ...

# kotlin-native

[Animesh Sahu]

Can I debug it further, I don't see where could a worker be leaked?

Unfinished workers detected, 1 workers leaked!
Use `Platform.isMemoryLeakCheckerActive = false` to avoid this check.

Here's a small repro:

object Testing {
    val event = MutableSharedFlow<Int>(extraBufferCapacity = 8)

    init {
        event.subscriptionCount
                // .onEach { println("Subscription Count: $it") }  // Stub, For seeing the behavior
                .launchIn(CoroutineScope(Dispatchers.Unconfined))
    }
}

fun main() = runBlocking {
    Testing
}

Edit: Sometimes the following error is generated as well:

Memory leaks detected, 76 objects leaked!
Use `Platform.isMemoryLeakCheckerActive = false` to avoid this check.

[Animesh Sahu]

Issue submitted: KT-43771 and KT-43772 both with minimal repro.

[Dominaezzz]

You're not cancelling the scope before exit.

[Animesh Sahu]

Do I need to? By the way it doesn't happen if I use class and instantiate it instead using the singleton...

[Animesh Sahu]

Which issue you're talking about 😅, I replied in context of the one with memory leak (not one with worker thread)

[Dominaezzz]

Yeah the leak. You've got to free the coroutine.

[Dominaezzz]

I'm talking about the code on slack, haven't looked at the tickets yet.

[Animesh Sahu]

Ohh, thanks!

[Animesh Sahu]

But unlike JVM I can't add a hook to run at the termination for cleanup, any suggestion for the cleanup?

[Animesh Sahu]

In such a situation where I'm developing a lib and the consumer don't have access to the internals (those scopes), if I want to clear the memory before the exit...

[Dominaezzz]

Provide a close method. I think users should be somewhat aware of lifecycles.

[Animesh Sahu]

@Dominaezzz Any thoughts on the worker leaks? That still happens if cancelled the CoroutineScope

[Dominaezzz]

Not sure tbh. Haven't really used coroutines on native.

[napperley]

Not a good idea to mix Workers and Coroutines together. Coroutines work fine with Kotlin Native, and don't require Workers to run.

[Animesh Sahu]

@napperley sorry for late reply (apparantly I forgot to see the reply), but workers aren't involved anywhere, the leak is from internals of coroutines, see the repro I've shown: KT-43772