-
Notifications
You must be signed in to change notification settings - Fork 1.9k
DumpCoroutineInfoAsJsonAndReferencesTest.testDumpWithNoCoroutines
spuriously fails on Mac OS X
#3028
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
Labels
Comments
Interesting part of
Seems like in some circumstances |
qwwdfsad
added a commit
that referenced
this issue
Nov 17, 2021
Otherwise, multiple pairs of install + uninstall may leave multiple cleanup threads in the state when the map is already cleaned up, but its size is not Fixes #3028
qwwdfsad
added a commit
that referenced
this issue
Nov 17, 2021
Otherwise, multiple pairs of install + uninstall may leave multiple cleanup threads in the state when the map is already cleaned up, but its size is not Fixes #3028
qwwdfsad
added a commit
that referenced
this issue
Nov 19, 2021
* Try to trim memory usage of Dokka and Lincheck * Disable failing test * Do avoid concurrent-unsafe Collections.toList for working with ConcurrentWeakMap.keySet * Do join weakRefCleanerThread in DebugProbes.uninstall Otherwise, multiple pairs of install + uninstall may leave multiple cleanup threads in the state when the map is already cleaned up, but its size is not Fixes #3028
Fixed |
yorickhenning
pushed a commit
to yorickhenning/kotlinx.coroutines
that referenced
this issue
Jan 28, 2022
* Try to trim memory usage of Dokka and Lincheck * Disable failing test * Do avoid concurrent-unsafe Collections.toList for working with ConcurrentWeakMap.keySet * Do join weakRefCleanerThread in DebugProbes.uninstall Otherwise, multiple pairs of install + uninstall may leave multiple cleanup threads in the state when the map is already cleaned up, but its size is not Fixes Kotlin#3028
pablobaxter
pushed a commit
to pablobaxter/kotlinx.coroutines
that referenced
this issue
Sep 14, 2022
* Try to trim memory usage of Dokka and Lincheck * Disable failing test * Do avoid concurrent-unsafe Collections.toList for working with ConcurrentWeakMap.keySet * Do join weakRefCleanerThread in DebugProbes.uninstall Otherwise, multiple pairs of install + uninstall may leave multiple cleanup threads in the state when the map is already cleaned up, but its size is not Fixes Kotlin#3028
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: