-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Memory leak in namespaces #608
Comments
Thank you for this. I'll try reproducing and get back to you shortly. |
einaros
added a commit
to einaros/socket.io
that referenced
this issue
Oct 31, 2011
That ought to cover it. |
Awesome! I can't help thinking though that it might also be beneficial to not insert the socket object into the other namespaces in the first place. Is this possible or have I mis-understoud how a part of the system works? |
This was referenced Nov 21, 2022
darrachequesne
pushed a commit
that referenced
this issue
Jul 4, 2024
fix a namespace connection error
darrachequesne
pushed a commit
that referenced
this issue
Jul 8, 2024
The `main` entry for the `package.json` file is for defining the entry point. The entry is currently missing the required `.js` extension, this PR brings it back.
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
While trying to produce a list of sockets currently connected to the server I discovered a minor memory leak. When using several namespaces, for some reason each connection to the server creates a new socket instance in each namespace's object, despite only one being required.
When the client disconnects, only the specified namespace's socket object is removed, all the other namespaces are left with an empty socket instance with disconnected == false.
This can be seen by listing a namespaces sockets, connecting to a different namespace, closing, then refreshing the first namespaces sockets list. Quick pseudo example:
Cheers,
sam
The text was updated successfully, but these errors were encountered: