Repository navigation
4.x: Cache/Replay operators to be more GC friendly #7912
Description
The current implementations of the various cache and replay operators and hot sources can hold onto effectively unreachable elements longer than necessary, causing GC pressure with certain collectors.
The following operators need to be checked and updated.
-
ObservableCache -
FlowableCache -
ObservableReplay -
FlowableReplay -
ReplaySubject -
ReplayProcessor
Activity
akarnokd commentedon Oct 2, 2025
ObservableCache- #7911DragonFSKY commentedon Jul 27, 2026
I'd like to work on the FlowableCache item in #7912, using the ownership split from ObservableCache #7911 while preserving Flowable's per-subscriber request, cancellation, and serialized replay semantics. I'll add the same focused MemoryMXBean/System.gc regression test. Please let me know if someone is already working on this item.
akarnokd commentedon Jul 27, 2026
No one is working on these currently so go ahead 👍
[-]Cache/Replay operators to be more GC friendly[/-][+]4.x: Cache/Replay operators to be more GC friendly[/+]Use the RxJava 4 core connectable types in regression
Release cancelled replay consumers from their buffers
Release cancelled replay consumers from their buffers
Release cancelled replay consumers from their buffers
Follow validator upstream naming convention in replay fixture
Release cancelled replay consumers from their buffers (#8317)