Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ws error: RangeError: out of range index #58

Open
zlatinov opened this issue Nov 14, 2016 · 2 comments
Open

ws error: RangeError: out of range index #58

zlatinov opened this issue Nov 14, 2016 · 2 comments

Comments

@zlatinov
Copy link

zlatinov commented Nov 14, 2016

Windows 10, node v6.5.0, npm 3.10.5
The app is crashing in random times with this error:

Project\node_modules\telehash\node_modules\telehash-http\node_modules\socket.io-client\node_modules\engine.io-client\node_modules\ws\l
ib\Receiver.js:323
    default: srcBuffer.copy(dstBuffer, dstOffset, 0, length); break;
                       ^

RangeError: out of range index
    at RangeError (native)
    at fastCopy (Project\node_modules\telehash\node_modules\telehash-http\node_modules\socket.io-client\node_modules\engine.io-client\
node_modules\ws\lib\Receiver.js:323:24)
    at Receiver.add (Project\node_modules\telehash\node_modules\telehash-http\node_modules\socket.io-client\node_modules\engine.io-cli
ent\node_modules\ws\lib\Receiver.js:84:3)
    at Socket.firstHandler (Project\node_modules\telehash\node_modules\telehash-http\node_modules\socket.io-client\node_modules\engine
.io-client\node_modules\ws\lib\WebSocket.js:678:22)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:176:18)
    at Socket.Readable.push (_stream_readable.js:134:10)
    at TCP.onread (net.js:543:20)
@ig0r
Copy link

ig0r commented Nov 15, 2016

I'm observing the same behaviour on Linux as well. Usually happens after uptime for 2-4 hours

@anhldbk
Copy link

anhldbk commented Dec 30, 2016

@zlatinov , @ig0r : Looks like an error of package socket.io-client. Anway, this repo seems to not maintained well. I wonder if we should use it in production.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants