A modern programming language that makes developers happier.

kotlinlang

Yesterday I ran into a bug with `runBlocking`
In my program I have a top level coroutine dispatcher that uses `runBlocking` as an event loop for the main thread. 
In the application code, it uses `runBlocking` somewhere else for something more trivial. 
It seems that the dispatcher for the 2 contexts are sharing some state. It runs a few main loop frames when the second `runBlocking` is called.
Moreover, the stacktrace in intellij, which says async stack trace, doesn't indicate any difference when the main loop is executed in this way.

Maybe you could share some sample. Why do you use runBlocking for event loop?

It's a desktop application that uses OpenGL