Vsevolod Tolstopyatov

(adding myself as a watcher, won't do the review)

Thanks for the detailed report! @dkhalanskyjb who is the main maintainer of the test module is on vacation right now, so delayed (he-he) answer here is expected

Thanks!

Steps to reproduce: * add `while (true)` to `RunningThreadStackMergeTest` * Re-run it once every 5 secs, the bug reproducer only before C2 JIT kicks in Failing build https://teamcity.jetbrains.com/buildConfiguration/KotlinTools_KotlinxCoroutines_Build/3793970?showRootCauses=false&expandBuildChangesSection=true&expandBuildProblemsSection=true&expandBuildTestsSection=true

This is not an inconsistency, but rather a semantic difference: see https://github.com/Kotlin/kotlinx.coroutines/pull/2964 with an explanation and https://github.com/Kotlin/kotlinx.coroutines/issues/2942 with actual rationale. Documentation could've been better here though. > I guess it...

Could you please elaborate on what exactly do you mean? You can use `Executor.asCoroutineDispatcher` and configure the thread factory to set any named you want to the corresponding threads

Could you please elaborate on for what purpose do you need a configurable `Dispatchers.Default` name?

Thanks for the explanation and also a reminder about scheduler configurability via system props! The system property is indeed can be a way to go here

Hi, this is clearly an Android bug that should be reported to Google bug tracker, we cannot do much on our side here. >I wonder if an option to disable...

Thanks! Please keep us informed about this problem. Let's leave it open for a while to see if there are other similar reports