-
-
Notifications
You must be signed in to change notification settings - Fork 123
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
WebsocketProvider not destroyed #636
Comments
+1 I've been meaning to make a ticket about this, I'm manually destroying the websocket provider at the same time in our application. |
I think the problem in here. |
hmm yep we're still lacking documentation for this unfortunately. It's intended behavior as the socket can be created without a document connected/connecting (and should survive a document being destroyed as you can just open another one) If you want to close the connection, you need to destroy the websocket provider as well ( |
I agree with the intended behavior described above but I noticed something else that seems unexpected. I'm reusing single For example, Here handler is configured, but
Will try to provide a minimal repro soon. |
Closing this, as the behaviour is intended. The memory leak has already been fixed by @raineorshine :) |
Description
HocuspocusProviderWebsocket is not destroyed when HocuspocusProvider's destroy is called.
Steps to reproduce the bug
Steps to reproduce the behavior:
Expected behavior
HocuspocusProviderWebsocket is destroyed
Screenshot, video, or GIF
If applicable, add screenshots to help explain your problem.
Environment?
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: