-
Notifications
You must be signed in to change notification settings - Fork 148
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
[Bug] IllegalReferenceCountException: refCnt: 0 in netty encode message #1127
Comments
The |
The memory won't be released in some cases if the memory isn't allowed to release by users. |
The variable |
I didn't find we set this variable. And the concrete byte buf is |
If we use HeapByteBuf, we don't enable off heap memory. |
Oh, it's just tmp data. |
What do you mean? Sorry I'm not familiar with netty. |
My mistake, igore it. |
Could you help check this failure? @leixm |
Sure, i will check this failure. |
…ta in client side (#1150) ### What changes were proposed in this pull request? The principle of data being released is that the data has been sent. However, under the current implementation, all blocks will be released in the last event. Once executed out of order, the unsent block data will be released prematurely, which is wrong. ### Why are the changes needed? Fix: #1127 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? 1. existing UTs
Code of Conduct
Search before asking
Describe the bug
Affects Version(s)
master
Uniffle Server Log Output
No response
Uniffle Engine Log Output
No response
Uniffle Server Configurations
No response
Uniffle Engine Configurations
No response
Additional context
No response
Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: