We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After experiencing high traffic, when the connection becomes idle, the memory in the ringbuf still cannot be released.
Emerged after solving the problem #659
v2
v2.6.1-cache-fix
Linux
Linux 6.2.0-39-generic x86_64
1.21.6
1
After experiencing high traffic, when the connection becomes idle, the memory in the ringbuf still cannot be released
It can reproduce with the latest release
The text was updated successfully, but these errors were encountered:
v2.6.2 should have fixed this issue, please try it out and let me know if it works.
Sorry, something went wrong.
Alright, I'll give it a try and get back to you later.
like nice.
panjf2000
No branches or pull requests
Actions I've taken before I'm here
What happened?
After experiencing high traffic, when the connection becomes idle, the memory in the ringbuf still cannot be released.
Emerged after solving the problem #659
Major version of gnet
v2
Specific version of gnet
v2.6.1-cache-fix
Operating system
Linux
OS version
Linux 6.2.0-39-generic x86_64
Go version
1.21.6
Relevant log output
Code snippets (optional)
1
How to Reproduce
After experiencing high traffic, when the connection becomes idle, the memory in the ringbuf still cannot be released
Does this issue reproduce with the latest release?
It can reproduce with the latest release
The text was updated successfully, but these errors were encountered: