socket.io icon indicating copy to clipboard operation
socket.io copied to clipboard

Published 20 hours ago • verified publisher icon socketio

If the server's upstream bandwidth is used up, it will generate a large number of pingTimeoutTimers, which in turn will cause memory leaks

Open introspection3 opened this issue 1 year ago • 1 comments

Describe the bug If the server's upstream bandwidth is used up, it will generate a large number of pingTimeoutTimers, which in turn will cause memory leaks

To Reproduce

If the server's upstream bandwidth is used up, it will generate a large number of pingTimeoutTimers,

Socket.IO server version: 4.5

image

Expected behavior work

Platform: debian

  • Device: [e.g. Samsung S8]
  • OS: [e.g. Android 9.2] debian

Additional context Add any other context about the problem here.

introspection3 avatar Jan 31 '24 04:01 introspection3

When the bandwidth is used up, I think that the heartbeat mechanism will fail and the connections will be closed with the reason "ping timeout", and then everything should be properly garbage collected. Isn't that what you are experiencing?

Reference: https://nodejs.org/en/guides/diagnostics/memory/

darrachequesne avatar Feb 01 '24 07:02 darrachequesne