MemoryPool in SocketConnectionListener leaks after high load #28560
Labels
area-networking
Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions
✔️ Resolution: Duplicate
Resolved as a duplicate of another issue
Status: Resolved
Describe the bug
I found lots of memory doesn't get gc after a very high load testing (More than 30000 websocket connections and concurrent sending message every 1 second on a 8 cores VM).
I got a dump after testing and found MemoryPool in SocketConnectionListener consumes a lot of memories.
To Reproduce
Further technical details
The text was updated successfully, but these errors were encountered: