Today, it is still the case that the missing stack...
# coroutinesc
CLOVIS
08/04/2025, 2:07 PMToday, it is still the case that the missing stacktraces when using coroutines are a major blocker for adoption in many teams. Are there plans on providing a mode in which stacktraces are correct (even if that's slower)?
r
reformator
08/04/2025, 2:12 PMthere was a new release today https://github.com/Anamorphosee/stacktrace-decoroutinator
c
CLOVIS
08/04/2025, 2:12 PMI know about Decoroutinator, but it's JVM-only and from what I remember it doesn't work with profilers
r
reformator
08/04/2025, 2:13 PMbut it's JVM-onlyJVM and Android
c
CLOVIS
08/04/2025, 2:14 PMSure, but that's basically the JVM
CLOVIS
08/04/2025, 2:15 PM(this is not a critique of Decoroutinator btw, the method they're using wouldn't work on non-JVM platforms, it's already quite impressive that it does work)
CLOVIS
08/04/2025, 2:16 PMProfiling is particularly important to us. Coroutines are supposed to be for the performance-minded, but once you adopt them, it's impossible to know about your performance hot spots anymore.
z
Zach Klippenstein (he/him) [MOD]
08/04/2025, 3:31 PM> Coroutines are supposed to be for the performance-minded
Where did you hear this lol. Nothing about coroutines is inherently performance-related. The closest thing would be potentially increasing throughput vs one-thread-per-task but that’s been a terrible model for a long time and there have been solutions to it way before coroutines.
👎 1
2 Views