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

Assertion fail (still), Websocket and Chrome 11.0.696.71 #231

Closed
tronning opened this issue May 31, 2011 · 1 comment
Closed

Assertion fail (still), Websocket and Chrome 11.0.696.71 #231

tronning opened this issue May 31, 2011 · 1 comment

Comments

@tronning
Copy link

Seen similar been reported as resolved but I still get an aborted server from calling it from Chrome 11.0.696.71 via websocket.

node: ../src/node.cc:1212: ssize_t node::DecodeWrite(char*, size_t, v8::Handlev8::Value, node::encoding): Assertion `b[1] == 0' failed.

Running Socket.io 0.6.18 via npm on Node.js 0.4.8
Other browsers/transports work fine.

/tim

@tronning
Copy link
Author

Odd but for some reason my two installs of Node on my box is out of sync. A compiled version under a test user is now 0.5.0.PRE versus my gentoo package which is 0.4.8. Do not understand how the 0.5 got in there. Anyway, the Gentoo 0.4.8 package works fine with websocket on Chrome.

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

1 participant