AssertionError crash at ServerResponse.resOnFinish

Running io.js 3.2 installed from source on a centOS 7 machine, here are the logs:
http://pastebin.com/ix0Ke5zS

I was fiddling around with my server on digital ocean and got this screen when checking out their embedded terminal.
http://i.imgur.com/d0jc9zG.png
Could it be insufficient RAM that caused the crash? I am running a mongodb instance on the server and using libraries that are a little bulky on RAM.
I checked the RAM usage once and I had around 70 or 50 MB idle. I wasn`t looking how much RAM I had free at the time of the crashes.

Edit: total RAM of the server is 512.

[mscdex]

Did you try with other versions, like io.js 2.5.0?

No, this just happened on a live instance. I have been running 3.2 on a different instance until yesterday, but the other machine had 1gb RAM. I will try upgrading the server and see if it happens again.

Yeah, people have been posting and so far, so good. "top" indicates about 400MB free RAM, so I really guess the issue was with RAM causing trouble down the road.
I don't know if its possible for io.js to handle that and give a more intuitive error. If it is, it could be useful in a scenario like this.

Actually, it still crashes, just isn't so often so the application will stop.
Edit: it just caused it to stop again.

Crashed with 3.3.0, trying with 2.5.0.

Edit: so far, it seems 2.5.0 is going through the same scenarios that caused 3.x to crash and there was absolutely zero failures so far.

Update: someone pointed digital ocean doesn`t give you swap memory. So it might be possible the crashes were caused by a RAM peak?

[arthurschreiber]

We see the same error with Node 4.0 on our RHEL 6 machines. We haven't seen this issue with io.js 2.5.0.

[arthurschreiber]

This seems to be related to #1411. @indutny Any idea what's happening here?

Stacktrace:

AssertionError: false == true
    at ServerResponse.detachSocket (_http_server.js:144:3)
    at ServerResponse.resOnFinish (_http_server.js:483:11)
    at emitNone (events.js:67:13)
    at ServerResponse.emit (events.js:166:7)
    at finish (_http_outgoing.js:526:10)
    at doNTCallback0 (node.js:407:9)
    at process._tickDomainCallback (node.js:377:13)

[fasiha]

I'm running into the same issue with node 4.1.0 using just Express. Looks like socket.io folks are seeing this too: socketio/socket.io#2236 😭 Definitely not RAM: 16 GB here.

[fasiha]

I may have fixed it with an npm update to pull in updated dependencies (instead of just using whatever version was saved when I did npm install X --save who-knows-when).

[simplier]

I'm running into the same issue with iojs 3.0.0 :( Any update on this?

@fasiha how are you going with npm update?