-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
Multiple gateways with socket.io get (disconnect listeners added to [Socket]) #7287
Comments
16-gateways-ws.zip |
Is this related to #7249? |
Looks like it is related.. But not 100% sure |
Can you please provide a minimum reproduction repository (and make it available through Github)? |
@kamilmysliwiec I updated the issue 13 days ago with repo and project that reproduce. |
@kamilmysliwiec Any updates? Maybe this issue needs another label? |
I believe it is related to: #6026 (comment) |
Let's track this here #7249 |
Bug Report
Current behavior
Using multiple gateway (Same socket io server).
When there a connection we get 'Possible EventEmitter memory leak detected. X disconnect listeners added to [Socket]'
It looks like for every gateway for every connection is subscribed to disconnect event(Also connect). Look on image below:
image
The file is ws-adapter.js
Expected behavior
Not to get this warning or at least understand what can cause it and what is the risk
Possible Solution
N/A
Environment
Nest version: 7.6.11
I also tried to update to latest but with no success
For Tooling issues:
Attached example project that reproduce this issue.
When you start the project you can see the warning on logs..
https://github.com/nestjs/nest/issues/7228
The text was updated successfully, but these errors were encountered: