-
Notifications
You must be signed in to change notification settings - Fork 80
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
Rx WorkflowHost adapters swallow "Fatal" (as def'd by Rx2) exceptions from subscribers. #399
Comments
The exception is pretty clearly a compiler bug, I'll get that reported. Goes away if I change the UpdateTools interface in ViewStateCache to a data class -- probably a problem w/anonymous objects in lambdas. |
If I explicitly throw a IntelliJ will occasionally suck up all my CPU and hang while stepping around after the RxJava is seeing the error as a |
I can't repro in a clean room project, and the code that it is occuring in ( |
I reproduced in unit tests: 86b82bc Going to replicate these tests for (our internal-only, for now) |
Working around this internally by checking for this condition and manually passing to the thread's I've also reproduced the bug in an isolated project and filed as Kotlin/kotlinx.coroutines#1297. |
Finally got around to reporting the swallowed exception to JetBrains, https://youtrack.jetbrains.com/issue/KT-32351 |
@zach-klippenstein we can close this now, yeah? |
I want to leave this open until I'm able to remove our workarounds (I think using Flow should fix). |
ray/DNM-swallowed-exception
Now uncomment the block at line 47 of
MainActivity
, to make another subscription toworkflowRunner.renderings
. Repeat the recipe, and crash (stack below).I suspect that in the hang recipe this exception is being swallowed, but I haven't dug further yet.
The text was updated successfully, but these errors were encountered: