Skip to content
This repository has been archived by the owner on Apr 15, 2021. It is now read-only.

Connecting and disconnecting to the same process multiple times causes event emitter leak warnings #1

Open
qdot opened this issue Apr 14, 2019 · 0 comments
Labels
bug Something isn't working

Comments

@qdot
Copy link
Contributor

qdot commented Apr 14, 2019

Server using string based output.
Starting insecure websocket server
Insecure server listening on port 12345
(node:11037) UnhandledPromiseRejectionWarning: Error: WebSocket is not open: readyState 2 (CLOSING)
    at WebSocket.send (/snapshot/intiface-cli-node/node_modules/ws/lib/websocket.js:329:19)
    at WebSocketServer.<anonymous> (/snapshot/intiface-cli-node/node_modules/buttplug-node-websockets/dist/src/ButtplugNodeWebsocketServer.js:122:32)
    at Generator.next (<anonymous>)
    at fulfilled (/snapshot/intiface-cli-node/node_modules/buttplug-node-websockets/dist/src/ButtplugNodeWebsocketServer.js:11:58)
    at process._tickCallback (internal/process/next_tick.js:68:7)
(node:11037) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:11037) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
^CShutting down
Stopping websocket server
@qdot qdot added the bug Something isn't working label Apr 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant