Skip to content

Memory leak when using subscription with distinctUntilChanged #2092

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
JajaComp opened this issue Apr 23, 2025 · 0 comments
Open

Memory leak when using subscription with distinctUntilChanged #2092

JajaComp opened this issue Apr 23, 2025 · 0 comments
Labels
type: bug Something isn't working

Comments

@JajaComp
Copy link
Contributor

Library Version
8.4.0

Describe the bug
If using subscription flow with distinctUntilChanged() after crash client - flow still work

To Reproduce
Launch server. Launch client. Wait 5 second until client will stop or kill client process after few seconds. In server process flow still will work

fail_demo.zip

@JajaComp JajaComp added the type: bug Something isn't working label Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Development

No branches or pull requests

1 participant