WebsocketProvider not destroyed about hocuspocus HOT 5 CLOSED

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 (socket.disconnect() or socket.destroy()). Documentation is in the process ..

from hocuspocus.

Closing this, as the behaviour is intended. The memory leak has already been fixed by @raineorshine :)

from hocuspocus.

+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.

from hocuspocus.

I think the problem in here.
#637

from hocuspocus.

I agree with the intended behavior described above but I noticed something else that seems unexpected.

I'm reusing single HocuspocusProviderWebsocket across multiple HocuspocusProvider instances and then manually destroy these when required (onBeforeUnmount hook in Vue). But it seems that provider doesn't unsubscribe properly from websocketProvider which leads to a memory leak.

For example, onStatus hook will still be called for websocket reconnect events later even after HocuspocusProvider has been explicitly destroyed.

Here handler is configured, but this.removeAllListeners() in destroy call won't unsubscribe this.

Will try to provide a minimal repro soon.

from hocuspocus.