Skip to content

Make ReplayBufferBase propagate events without holding onto its lock - #2714

Closed
isaac-weisberg wants to merge 1 commit into
ReactiveX:mainfrom
wesprint-io:isaac/ReplayBufferBase-propagate-outside-lock
Closed

isaac-weisberg wants to merge 1 commit into
ReactiveX:mainfrom
wesprint-io:isaac/ReplayBufferBase-propagate-outside-lock

Conversation

@isaac-weisberg

@isaac-weisberg isaac-weisberg commented Jun 3, 2026 •

Copy link
Copy Markdown
Contributor

Otherwise, it can create deadlock situations

Fixes #2713

@freak4pc

Copy link
Copy Markdown
Member

Merged via #2723 with your commits' authorship preserved — closing as superseded. Thanks again for the diagnosis and the fix! Regression tests for all five lock inversions are on main now, and CI is green again as of #2726.

@freak4pc freak4pc closed this Aug 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ReplayBufferBase can create deadlocks

2 participants