You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I'm looking to convert my Singles, Maybes, and Completables into suspend functions, while still relying on RxJava's Observables, I was hoping that CoroutineScope could manage the subscription to my Observable streams by relying on the consumeEach extension function. However, it turns out that when the Job gets cancelled, although no more values will be "consumed" by the underlying Channel, the Observable itself will not get disposed. This could potentially leak the Observable.
Fixed bugs in MaybeSource/ObservableSource.consumeEach implementation
so that observable is disposed on cancellation.
Also optimized implementation of bridge function to avoid extra dispose
calls if possible (this is permissible by specification, though)
Fixes#1008
Fixed bugs in MaybeSource/ObservableSource.consumeEach implementation
so that observable is disposed on cancellation.
Also optimized implementation of bridge function to avoid extra dispose
calls if possible (this is permissible by specification, though)
Fixes#1008
Fixed bugs in MaybeSource/ObservableSource.consumeEach implementation
so that observable is disposed on cancellation.
Also optimized implementation of bridge function to avoid extra dispose
calls if possible (this is permissible by specification, though)
Fixes#1008
As I'm looking to convert my
Singles
,Maybes
, andCompletables
intosuspend
functions, while still relying on RxJava'sObservables
, I was hoping thatCoroutineScope
could manage the subscription to myObservable
streams by relying on theconsumeEach
extension function. However, it turns out that when theJob
gets cancelled, although no more values will be "consumed" by the underlying Channel, theObservable
itself will not get disposed. This could potentially leak theObservable
.Sample Repro:
When I run this test I get the following result:
The text was updated successfully, but these errors were encountered: