Skip to content

Release SetupFrame on RSocket version mismatch #472

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

Merged
merged 1 commit into from
Mar 5, 2018

Conversation

mostroverkhov
Copy link
Member

@mostroverkhov mostroverkhov commented Mar 5, 2018

Closes #471

@yschimke
Copy link
Member

yschimke commented Mar 5, 2018

IIUC: Offsets retain in NettyDuplexConnection and WebsocketDuplexConnection receive()

@yschimke yschimke merged commit 80c9b58 into rsocket:1.0.x Mar 5, 2018
@yschimke
Copy link
Member

yschimke commented Mar 5, 2018

@mostroverkhov do you think it is viable to verify the Buf reference counting in our existing tests?

@mostroverkhov
Copy link
Member Author

@yschimke SETUP_VERSION is hardcoded deeply in SetupFrameFlyweight - I can expose It in Frame.Setup.from() and add appropriate tests in follow-up PR.

@yschimke
Copy link
Member

yschimke commented Mar 5, 2018

I was more wondering whether any of existing tests could check for memory leaks at the end of a run? I'm happy with your bug fix as is, if tests are still passing, I believe it means you haven't corrupted something.

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.

2 participants