https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
x

xenomachina

03/11/2021, 5:18 PM
How does one debug deadlocks in coroutines? What I'd like to be able to do is run the code until it deadlocks, and see a snapshot of where each coroutine is "stuck". The coroutines tab in the debugger doesn't work, so I've just been adding logging around every suspend point I think could be responsible. This "works", but is incredibly tedious and slow, and also error-prone because it'll fail if I don't think of the guilty suspend point when adding my logging. Is there a better way?
l

louiscad

03/11/2021, 5:28 PM
If you use
Mutex
, know that it is not reentrant.
x

xenomachina

03/11/2021, 5:31 PM
No
Mutex
, just using channels.
l

louiscad

03/11/2021, 5:34 PM
Channels are often best kept as an implementation detail. Once you do this, you just have to think: Is there something that waits for something else that waits for that something? Another possible thing that might seem like a deadlock is an infinite loop, for example because of a special condition changing, or a function no longer suspending, or a
CancellationException
not caught when it should not, and not rethrown.
x

xenomachina

03/11/2021, 5:36 PM
I'm not sure what you mean by "Channels are often best kept as an implementation detail".
l

louiscad

03/11/2021, 5:38 PM
If all of your codebase uses
Channel
, kinda like event buses, then it's harder to figure things out. Often, you can hide it in internals, behind a façade that exposes safer things like plain suspending functions, or
Flow
s, where it's unlikely you can get deadlocks.
x

xenomachina

03/11/2021, 5:44 PM
Ah, yeah, I'm building something that uses channels internally, but uses regular suspend functions for the most part. I haven't found a use for flows just yet.
In any case, I know what can cause deadlocks, the issue is that if there's a bug that's causing a deadlock I don't see how to diagnose the problem without adding printfs everywhere.
l

louiscad

03/11/2021, 5:46 PM
Flows are asynchronous sequences, that's it. Useful for reactive programming, like reacting to a value change, do some operations based on some sequence of values, listen to changes from mutliple sources…
Are these suspending deadlocks or thread /locks related deadlocks?
x

xenomachina

03/11/2021, 5:47 PM
Aren't channels also asynchronous sequences?
l

louiscad

03/11/2021, 5:48 PM
Channels are hot, unlike flows. Channels are more like BlockingQueue, and Flows, more like Sequence or Stream.
x

xenomachina

03/11/2021, 5:48 PM
I have no idea. I can't debug it. One of my unit tests just stops doing anything. If I pause in the debugger, I'm in
sun.misc.Unsafe.park()
.
l

louiscad

03/11/2021, 5:49 PM
It always arrives in
park?
x

xenomachina

03/11/2021, 5:50 PM
As far as I can tell, yes.
l

louiscad

03/11/2021, 5:52 PM
Then you'll need to log things to find what never resumes.
What platform are you on?
JVM or Android?
x

xenomachina

03/11/2021, 5:53 PM
JVM (on Linux)
l

louiscad

03/11/2021, 5:54 PM
You can make an inline
withLog(…) { }
function that has a try catch finally block (and rethrows after logging), so it's less code to log entry/exit of suspend calls that might be the culprit.
x

xenomachina

03/11/2021, 6:00 PM
Yeah, I've done that. Relying on debug logging just seems like a big step back. It's incredibly tedious. The broken exception stack traces also make debugging a challenge.
l

louiscad

03/11/2021, 6:02 PM
Debug logging has never been deprecated 😄
x

xenomachina

03/11/2021, 6:07 PM
True. Just seems I need to rely on it a lot more when working with coroutines.
l

louiscad

03/11/2021, 7:31 PM
I am personally fine with the debugger, setting breakpoints (not step by step though because it doesn't work over suspension points so far), and using evaluate expression, but depending on what you're doing, it might not be enough.
u

uli

03/11/2021, 9:50 PM
Are all the threads in
sun.misc.Unsafe.park()
?
x

xenomachina

03/11/2021, 10:11 PM
I just figured out what was going on with this one a couple of minutes ago. Turns out it wasn't really a deadlock. I'd run into this problem after dealing with a bunch of deadlocks, so I guess I had deadlocks on the brain. 🤦 What was actually happening: A test was waiting for something external to complete, and that thing was never completing. (I hadn't realized it had gotten this far, and was looking for a deadlock much earlier than this). It was doing roughly:
while (!isItDone()) {
    delay(100)
}
So when I was pausing in the debugger my test was inside the
delay(100)
, but unfortunately, the call stack in the debugger didn't show delay, or any of my code. Just the test framework, and about 5 other stack frames leading up to
park
.