You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did some profiling on our yjs websocket server and found that there is a memory leak present in there.
Even after the yjs ws session has ended, the library fails to de-reference its Yjs Doc objects leading them to pile up in memory.
I did some profiling on our yjs websocket server and found that there is a memory leak present in there.
Even after the yjs ws session has ended, the library fails to de-reference its Yjs Doc objects leading them to pile up in memory.
After careful debugging I have found that here is the issue - https://github.com/yjs/y-websocket/blob/master/bin/utils.js#L66
Perhaps we should use a weakmap? Is there any way to make sure when we call delete on this map we destroy all references.
The text was updated successfully, but these errors were encountered: