New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dispatchers.IO coroutine is blocked by load on Main #3038
Comments
See the workaround here: #2972 (comment) |
also it's for JavaFX coroutines |
Doesn't matter. The issue and the workaround are the same for any |
So i need to set the flag "kotlinx.coroutines.main.delay" - where I can set it? |
It is a system property: https://docs.gradle.org/current/userguide/build_environment.html#sec:gradle_system_properties Even though the workaround should fix this for you, could you please answer some questions to help us design the library?
Context: in the latest release candidate, we've made it so |
No the workaround doesn't work for me. even using 1.6.0-RC lib version |
What exactly are you doing?
I see, thanks! What is the purpose of the |
I start JavaFX app this way, also add setProperty to the di objects. Anyway I got the same behavior. I don't use |
Oh. In this case, maybe this issue is actually unrelated to #2972. A question I probably should've asked first: did the issue start happening after updating |
yes, first I discovered it using 'kotlinx-coroutines-javafx', version: '1.5.2' |
Ok, then the workaround I suggested definitely won't work. Did you ever see the good behavior in this case, or was the issue always present? |
My project is NDA, but I will prepare a project that will reproduce this behavior, but it requires custom HID device, not keyboard or mouse. Need some time to make a proper mock |
Closing as obsolete |
Hello, I'm trying to solve the incident. Some coroutine in IO dispatcher reads data from device, but if main thread got a lot of work to redraw - the IO coroutine will be blocked for the delay. on JVM 11
The device-reading coroutine works in DefaultDispatcher-worker-*
The text was updated successfully, but these errors were encountered: