ws: RangeError: out of range index crashing server
RangeError: out of range index
at RangeError (native)
at fastCopy (/Users/jmcnally/projects/nextlot-projects/nextlot-webcast-rtc/node_modules/ws/lib/Receiver.js:317:24)
at Receiver.add (/Users/jmcnally/projects/nextlot-projects/nextlot-webcast-rtc/node_modules/ws/lib/Receiver.js:78:3)
at Socket.firstHandler (/Users/jmcnally/projects/nextlot-projects/nextlot-webcast-rtc/node_modules/ws/lib/WebSocket.js:663:22)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at readableAddChunk (_stream_readable.js:177:18)
at Socket.Readable.push (_stream_readable.js:135:10)
at TCP.onread (net.js:542:20)
Not really sure what this means or how to fix, or where the problem is actually.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 18
- Comments: 29 (6 by maintainers)
Commits related to this issue
- Upgrade ws to 1.1.1 to fix RangeError crash We're seeing RangeError crashes intermittently when running Node 6.3+ along with this older version of WS. https://github.com/websockets/ws/issues/778 — committed to respoke/socket.io-client by chadxz 8 years ago
- updated ws version investigating https://github.com/websockets/ws/issues/778 — committed to LouDou/rethinkdb-websocket-client by deleted user 8 years ago
- updated ws version investigating websockets/ws#778 — committed to LouDou/rethinkdb-websocket-server by deleted user 8 years ago
- Prevent RangeError inside ws package Older versions of `ws` do not play well with newer versions of Node. https://github.com/websockets/ws/issues/778 @chadxz created an updated fork of socket.i... — committed to respoke/node-respoke-admin by ruffrey 8 years ago
- Upgrade ws Fixes RangeError: out of range index with ws and Node 6.something https://github.com/websockets/ws/issues/778 — committed to SignalK/signalk-js-client by tkurki 8 years ago
- Updated ws package version Updated websocket `ws` package version from 0.8.1 to 1.1.1 after stumbling upon a nasty application crash described here: https://github.com/websockets/ws/issues/778 Th... — committed to MonkeyDo/node-red by MonkeyDo 8 years ago
- A bug in websocket when using node 6.3+ https://github.com/websockets/ws/issues/778 /usr/local/lib/node_modules/tishadow/node_modules/ws/lib/Receiver.js:317 default: srcBuffer.copy(dstBuffer, dst... — committed to gimdongwoo/TiShadow by gimdongwoo 8 years ago
- cambio la version de ws debido a problemas en la conexion: https://github.com/websockets/ws/issues/778 — committed to Javier-Rotelli/taperbot by Javier-Rotelli 7 years ago
- Update to using ws@1.1.4 to avoid https://github.com/websockets/ws/issues/778 (#1691) websockets/ws#778 can cause ws to raise, terminating the python runtime. Upgrading ws avoids this. b/66429362 — committed to googledatalab/datalab by fischman 7 years ago
I use nvm to manage the node versions
upgrading to 1.1.1 resolved this issue for me.
I will agree that i am on 6.3.0, when i got the error with the < 1.0 ws.
My work around was to shrinkwrap and force update ws which otherwise seemed backwards compatible with the code depending on it.