purnaPrasanth
commented
2 years ago Seems like the issue happens when thread switching happens while onFailure is being executed. To demonstrate the case deterministically I have created a sample snippet,
import io.reactivex.Observable
import io.reactivex.Observer
import io.reactivex.Single
import io.reactivex.disposables.Disposable
import io.reactivex.exceptions.CompositeException
import io.reactivex.exceptions.Exceptions
import io.reactivex.plugins.RxJavaPlugins
import io.reactivex.schedulers.Schedulers
import java.util.concurrent.CountDownLatch
import java.util.concurrent.Executors
import java.util.concurrent.TimeUnit
fun main(args: Array<String>) {
val countDownLatch = CountDownLatch(1)
val disposable = SampleObservable()
.subscribeOn(Schedulers.io())
.subscribe(
{
println("Emitted")
countDownLatch.countDown()
},
{
println("Errored")
countDownLatch.countDown()
}
)
Single.just(Unit)
.delay(3000, TimeUnit.MILLISECONDS, Schedulers.io())
.subscribe({ disposable.dispose() }, {})
countDownLatch.await()
}
class SampleObservable : Observable<Unit>() {
override fun subscribeActual(observer: Observer<in Unit>?) {
observer?.onSubscribe(SampleCallback(observer))
}
private inner class SampleCallback(private val observer: Observer<in Unit>) : Disposable {
@Volatile
private var isDisposed: Boolean = false
init {
sendError(IllegalStateException("Sample Exception"))
}
override fun dispose() {
isDisposed = true
}
override fun isDisposed(): Boolean = isDisposed
private fun sendError(exception: Exception) {
if (!isDisposed) {
val executorService = Executors.newSingleThreadScheduledExecutor()
executorService.schedule(
{
try {
observer.onError(exception)
} catch (inner: Throwable) {
Exceptions.throwIfFatal(inner)
RxJavaPlugins.onError(CompositeException(exception, inner))
}
},
5,
TimeUnit.SECONDS
)
}
}
}
}The fix would be to synchronise read and writes to isDisposed and observer.
This is the cause for one of the top trending crashes in our product. Is the fix already in pipeline? Please advice any alternatives if possible. Thanks.
dbriggsDFleet
optisamit
tomridder
Test case/sample: https://gist.github.com/alapshin/a60540a1a128c0af042b7fe427b9de88
Description
RxJava3CallAdapterFactory.create()Result When call time outs Rx stream doesn't receive any event and remains active
Expected result When call time outs Rx stream receives error event and completes
Additional info If RxJava3 call adapter is created via
RxJava3CallAdapterFactory.createWithScheduler(Schedulers.io)then call cancellation by timeout produces exception which is propagated to streamThere is also somewhat related discussion at https://github.com/square/retrofit/issues/3453 with comment with comment https://github.com/square/retrofit/issues/3453#issuecomment-682034904 which points to possible cause of this difference in behavior.