[Bug]: Idle connections still occupy memory, the ringbuf cannot be released

[szza]

Actions I've taken before I'm here

• [X] I've thoroughly read the documentations on this issue but still have no clue.
• [X] I've searched the Github Issues but didn't find any duplicate issues that have been resolved.
• [X] I've searched the internet for this issue but didn't find anything helpful.

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

1

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

[panjf2000]

v2.6.2 should have fixed this issue, please try it out and let me know if it works.

[szza]

v2.6.2 should have fixed this issue, please try it out and let me know if it works.

Alright, I'll give it a try and get back to you later.

[szza]

v2.6.2 should have fixed this issue, please try it out and let me know if it works.

like nice.