2.x: fix replay().refCount() leaking items between connections #5182
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates
Observable.replay()
andFlowable.replay()
for 2.x to not leak items between reconnections when run with.refCount()
. Thereplay()
operator is designed to hold onto the buffer even after its completion so late subscribers can still receive the cached data. Only a newconnect()
clears this data which may or may not happen. SincerefCount
ensures that there won't be any latecommers to an already completed connection (because it also drops its current subscribers on termination or when reaching zero), thereplay()
can be reset to an empty state.Related: #5172, #5181.