Skip to content
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

Unclosed TCP connections #830

M4lik opened this issue Jan 30, 2019 · 1 comment


Copy link

@M4lik M4lik commented Jan 30, 2019


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:



This comment has been minimized.

Copy link

@M4lik M4lik commented Jan 30, 2019

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.

@h3poteto h3poteto added the Backlog label Feb 5, 2019
@h3poteto h3poteto added ToDo and removed Backlog labels Mar 10, 2019
@h3poteto h3poteto added Backlog and removed ToDo labels Aug 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.