Unclosed TCP connections

[dermalikmann]

Description

When you enable websocket Whalebird opens a new TCP connection every few seconds but doesn't close them. This leads to a lot of open connections which slowly but surely fills the servers RAM. Furthermore this effect seams to stack every time when you disable and reenable WS which leads to a DoS like behavior when executed a few times.

How To Reproduce

1. Open whalebird
2. Enable WS
3. Disable WS
4. Reenable
5. continue, watch server log gets flooded and server RAM filled.

Your Environment

• OS: Win10
• Whalebird Version: 2.6.2
• Instance: machteburch.social

[dermalikmann]

BTW: Usually we are around 100 simultaneous open TCP connections. The max peak there was around 13 000 simultaneous connections. And afaik: This was ONE client.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. You can remove the stale label with /remove-stale comment. Thank you for your contributions.