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
v

Vsevolod Ganin

12/05/2019, 11:06 AM
[v1.3.2] Can anybody explain why
CoroutineExceptionHandler
installed in top-most
runBlocking
is not being called? I read all docs but can’t quite grasp the sense of it. Example:
fun main(): Unit = runBlocking(CoroutineExceptionHandler { _, e ->
    println("Boom: $e")
}) {
    (0..10).map {
        launch {
            println("Throw in attempt #$it")
            throw RuntimeException("Attempt #$it")
        }
    }
    Unit
}
s

streetsofboston

12/05/2019, 12:49 PM
Yup, looks like your CEH should be called. Just curious, did you try providing your CEH to the ,
launc(ceh) {...}
instead?
v

Vsevolod Ganin

12/05/2019, 12:57 PM
Yes, still not working
Wrapping
launch
with
supervisorScope
helps though
s

streetsofboston

12/05/2019, 1:04 PM
Yeah, it works, but you created a brand new top-most scope..... Need to Google this... I can imagine a CEH is not necessary, because you can put a try-catch around the runBlocking and runBlocking only returns when all its children have finished (launch in this case)
v

Vsevolod Ganin

12/05/2019, 1:20 PM
Yeah, I can workaround that but now I’m studying how CEHs work and can’t quite understand the logic behind
s

streetsofboston

12/05/2019, 2:38 PM
I wrote a blog post about it, but only with regards to ‘launch’, ‘async’ and regular
suspend
functions and such: https://medium.com/the-kotlin-chronicle/coroutine-exceptions-3378f51a7d33
👍 1
v

Vsevolod Ganin

12/05/2019, 2:46 PM
I read your blogpost by the way 🙂 It was very enlightening at the point (along with blogspot https://medium.com/@elizarov/coroutine-context-and-scope-c8b255d59055)
s

streetsofboston

12/05/2019, 2:47 PM
Thanks! I should add a blurb about runBlocking….
v

Vsevolod Ganin

12/05/2019, 3:28 PM
Btw the whole story about top-most CEH is not working in action unfortunately. Check this example:
fun main(): Unit = runBlocking {
    val errorHandler = CoroutineExceptionHandler { _, e ->
        println("Boom: $e")
    }
    val scope = CoroutineScope(errorHandler)
    scope.launch {
        throw RuntimeException()
    }
    Unit
}
It does not crash and it does not print anything at all. The code is similar to one you have in the blogspot
s

streetsofboston

12/05/2019, 3:31 PM
This works:
fun main() {
    val ceh = CoroutineExceptionHandler { _, e ->
        println("CEH Handled Crash [$e]")  
    }

    CoroutineScope(context + ceh).launch {
        oops()
    }

    Thread.sleep(1000)
}
context
is just a dispatcher…
🤔 1
It seems
runBlocking
provides the top-most scope and it handles the exception. I think it just throws it to the caller of `runBlocking`…., even though you create a brand new top-scope right in your sample…. needs more investigation 🙂
v

Vsevolod Ganin

12/05/2019, 3:35 PM
Yeah maybe eventloop bootstrapped in
runBlocking
catches the exception
s

streetsofboston

12/05/2019, 3:37 PM
Could you try this; change
val scope = CoroutineScope(errorHandler)
into
val scope = CoroutineScope(otherDispatcher + errorHandler)
where
otherDispatcher
is a different dispatcher than the one the runBlocking is using…. It shouldn’t matter, but i’m curious….
v

Vsevolod Ganin

12/05/2019, 3:37 PM
Tried it, same behavior unfortunately
s

streetsofboston

12/05/2019, 3:38 PM
Well, at least that is to be expected, even though we may not like the answer 🙂 .
v

Vsevolod Ganin

12/05/2019, 3:38 PM
Debugger isn’t helping either. Next step after
throw
it disconnects 😞
s

streetsofboston

12/05/2019, 3:43 PM
https://stackoverflow.com/questions/53576189/coroutineexceptionhandler-not-executed-when-provided-as-launch-context > If a coroutine encounters exception other than CancellationException, it cancels its parent with that exception. This behaviour cannot be overridden and is used to provide stable coroutines hierarchies for structured concurrency which do not depend on CoroutineExceptionHandler implementation. The original exception is handled by the parent when all its children terminate. > This also a reason why, in these examples, CoroutineExceptionHandler is always installed to a coroutine that is created in GlobalScope. It does not make sense to install an exception handler to a coroutine that is launched in the scope of the main runBlocking, since the main coroutine is going to be always cancelled when its child completes with exception despite the installed handler
v

Vsevolod Ganin

12/05/2019, 3:49 PM
Ah I found my mistake. A subtle one. This prints:
fun main(): Unit = runBlocking {
    val errorHandler = CoroutineExceptionHandler { _, e ->
        println("Boom: $e")
    }
    val scope = CoroutineScope(errorHandler)
    scope.launch {
        throw RuntimeException()
    }.join()
    Unit
}
I added
join
And that was the reason why the debugger was disconnecting. With
join
I’m able to go further now
👍 1
a

alllex

12/05/2019, 4:19 PM
The code that you wrote in the very first message is perfectly fine. The documentation hints on why that is, but one needs to be very careful to find the hint. In my opinion the docs should be clearer. So, the docs say that this handler is only ever called for uncaught exceptions. Those are which would be swallowed without a trace or passed to Thread.uncaughtExceptionHandler if it is installed. The main (the only?) source of such uncaught exceptions is a
launch
running under a
SupervisorJob
. If you call
async
under supervisor, the exections are caught be the
Deferred
job, and will be rethrown when
await
is invoked. Therefore they are not “uncaught”. Calling both
launch
or
async
under a regular
Job
results in rethrown/propagated exceptions as well. Therefore they are not “uncaught” either. So, in your original example you either need to
launch
under a
supervisorScope
, or you need to wrap your
runBlocking
in try-catch. https://kotlin.github.io/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines/-coroutine-exception-handler/
v

Vsevolod Ganin

12/05/2019, 4:47 PM
This is perfect explanation, thank you! This perspective makes CEH a very weird tool. On one hand it seems like a tool designed to catch exception that you lost (as a programmer, should not happen), on the other you still can loose the exception, for example, if you forget to call
await
s

streetsofboston

12/05/2019, 4:57 PM
Calling
await()
allows you to try-catch an exception. Still, if the top-most scope called
launch
, its CEH will still be handling that exception. From my blog-post: > We need to be aware that even if we handle the exception by calling 
await()
, it will still go up the child-parent Coroutine chain.
v

Vsevolod Ganin

12/05/2019, 5:08 PM
But what if topmost coroutine is
async
? If we don’t call
await
the CEH on top will not get the exception. This is consistent with explanation above: the
async
handles the exception so it is not given to CEH. But if a user ceases to call
await
(let’s imagine he forgets) then the exception is lost. Example:
fun main() = runBlocking {
    val scope = CoroutineScope(CoroutineExceptionHandler { _, e ->
        println("Boom: $e")
    })
    scope.async {
        throw RuntimeException()
    }.join()
}
a

alllex

12/05/2019, 7:05 PM
In order to partially mitigate the issue with "forgetting to call await after async" Intellij (Kotlin?) provides a warning.