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
The handler will destroy the socket with an error argument. But according to Node's documentation in this case the error handler is invoked. See here This will again invoke the handler ad infinitum.
WebSocketConnection.prototype.handleSocketError=function(error){this._debug('handleSocketError: %j',error);if(this.state===STATE_CLOSED){// See https://github.com/theturtle32/WebSocket-Node/issues/288this._debug(' --- Socket \'error\' after \'close\'');return;}this.closeReasonCode=WebSocketConnection.CLOSE_REASON_ABNORMAL;this.closeDescription='Socket Error: '+error.syscall+' '+error.code;this.connected=false;this.state=STATE_CLOSED;this.fragmentationSize=0;if(utils.eventEmitterListenerCount(this,'error')>0){this.emit('error',error);}this.socket.destroy(error);/* <== HERE */this._debug.printOutput();};
The text was updated successfully, but these errors were encountered:
apirila
added a commit
to apirila/WebSocket-Node
that referenced
this issue
Oct 5, 2018
The error handler will cause an infinite loop. HandleSocketError method is attached as an error handler:
The handler will destroy the socket with an error argument. But according to Node's documentation in this case the error handler is invoked. See here This will again invoke the handler ad infinitum.
The text was updated successfully, but these errors were encountered: