Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

socket.io is crashing over https

See original GitHub issue

Note: for support questions, please use one of these channels: stackoverflow or slack

You want to:

report a bug
request a feature

Current behaviour

node: ../src/util-inl.h:196: TypeName* node::Unwrap(v8::Local<v8::Object>) [with TypeName = node::TLSWrap]: Assertion `(object->InternalFieldCount()) > (0)' failed.
Aborted

Steps to reproduce (if the current behaviour is a bug)

I have forked the code here:

https://github.com/dx9s/socket.io-fiddle/tree/issue-2999

make sure to checkout branch issue-2999

Expected behaviour

expect it not to crash like when server is running over http. Instead it crashes with the error listed above.

Setup

OS: Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial
browser: Firefox 54.0
socket.io version: 2.0.3

Other information (e.g. stacktraces, related issues, suggestions how to fix)

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

dx9scommented, Aug 29, 2017

@regimantas: Yeah, I figured updated the reference code project (which I have a commit pending now for over a month) that includes testing everything (SSL use - see https://github.com/dx9s/socket.io-fiddle/tree/issue-2999 ) would be a good “reference” update to help avoid people like you and me having same problem.

It boils down to is a problem with the Libraries (socket.io, etc.) or a problem with the runtime (nodejs), hence the reference code SSL addition.

1reaction

dx9scommented, Jul 7, 2017

Updated to latest version of nodejs from nodesource: $ $ node --version v8.1.3 and problem in my fork of socket.io-fiddle seems to work without crashing … tried my code and solved it. Sorry for the hassle. Hopefully others will find this and learn to update node first!

This issue can be closed!

Top Results From Across the Web

Troubleshooting connection issues | Socket.IO

First and foremost, please note that disconnections are common and expected, even on a stable Internet connection:

Socket.io - Prevent server crash if "client" emit wrong data

You can use Joi https://github.com/hapijs/joi. Joi allows you to define schema for input data and validate it with Joi.validate method ...

Implementing a Crash-Resistant Socket.io Service Without ...

Preserving State using FetchSockets. The first solution we considered to preserve state without using sticky routing is to use the data attribute on...

WebSockets in 100 Seconds & Beyond with Socket.io - YouTube

Learn the fundamentals of WebSockets in 100 seconds, then build a simple group chat app with Socket. io. https ://fireship.

Using WebSockets on Heroku with Node.js

Table of Contents. Create a new app; Option 1: WebSocket; Option 2: Socket.io. This tutorial will get you going with realtime ...