<@U2E974ELT> thanks for the detailed explanation. ...
# coroutines
m
@elizarov thanks for the detailed explanation. I guess my only worry is that in case
C
the stack is not printed at all since the program ends before the exception can be logged. I guess that the call to
CoroutineExceptionHandler
is not blocking/suspending, so that means that even if I set a custom
CoroutineExceptionHandler
it may not be executed completely if the app is about to end, the same way in my example it didn't get to complete the execution of the default implementation.