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

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

Open
introspection3 opened this issue Jan 31, 2024 · 1 comment

Comments

@introspection3
Copy link

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 introspection3 added the to triage Waiting to be triaged by a member of the team label Jan 31, 2024
@darrachequesne
Copy link
Member

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 darrachequesne added needs investigation and removed to triage Waiting to be triaged by a member of the team labels Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants