WebsocketProvider instance leaving open handles after calling .destroy in node.js about y-websocket

[dmonad]

It seems that it's the Awareness instance's fault. The Awareness instance is not destroyed because it could be used by other providers.

You will probably fix the issue by doing provider.awareness.destroy() before calling provider.destroy().

[dmonad]

Hi @kapv89, thanks for opening this issue. It would help me greatly if you could find out which handler is still open.

[kapv89]

hi @dmonad

below is the output from wtfnode

> [email protected] test
> node -r source-map-support/register -r dotenv/config dist/__tests__/main.js dotenv_config_path=.env.test.local

[1/1] app: single doc
Success: single doc in 1.06s
repeat: npm run test -- --filter "\[1/" 

All tests successful! in 1.06s
[WTF Node?] open handles:
- File descriptors: (note: stdio always exists)
  - fd 2 (tty) (stdio)
  - fd 1 (tty) (stdio)
- Sockets:
  - (?:?) -> localhost:? (destroyed)
  - 127.0.0.1:40838 -> 127.0.0.1:6379
  - 127.0.0.1:40840 -> 127.0.0.1:6379
- Timers:
  - (1 ~ 1 undefined) setupWS @ file:///home/k/Projects/proj/yjs-proto/exp/crdt-backend/node_modules/y-websocket/src/y-websocket.js:123
- Intervals:
  - (3000 ~ 3 s) (anonymous) @ file:///home/k/Projects/proj/yjs-proto/exp/crdt-backend/node_modules/y-protocols/awareness.js:59

I'll see what I can find, but cannot guarantee anything

[kapv89]

Thanks that fixes it. Closing the issue.