You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
The text was updated successfully, but these errors were encountered:
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?
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
Expected behavior
work
Platform: debian
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: