-
Notifications
You must be signed in to change notification settings - Fork 255
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
Release empty CompositeBuffers #238
Conversation
Thanks @alexwen for digging into this leak, I myself was behind this for a while but not able to point to the cause. Looking at the code, it appears to me that the check PS: Apologies for the delay in response, I was out on a vacation. |
It would be my preference as well to invokeContentOnNext unconditionally. It may break backwards compatibility in cases where folks might always be expecting the content to be readable, but it is a better behavcior, imo, to have it always emit one ByteBuf. The current behavior has forced me to put...
... throughout my code so I can do error handling irrespective of whether or not the server has returned a message. |
I agree, this is a better behavior. Do you want to update this PR with this change? |
Attempting this change leads to other issues downstream, it looks like they are originating from ServerSentEvents (as the observable now receives the empty byte buffer before the closing of the stream). I don't have time to look at this too deeply at the moment, but will update the issue if/when I can:
|
I am closing this PR in favor of #242, thanks for finding this out, anyways! |
No problem. Glad to see there will be a fix soon! |
Fix for #237
Release content if not readable.