timers.js:103 #1160

MSergW opened this Issue Feb 15, 2013 · 3 comments

3 participants


socket.io@0.9.13 node_modules/socket.io
├── base64id@0.1.0
├── policyfile@0.0.4
├── redis@0.7.3
└── socket.io-client@0.9.11 (xmlhttprequest@1.4.2, uglify-js@1.2.5, active-x-obfuscator@0.0.1, ws@0.4.25)

nodejs Node v0.8.20 (Stable)


if (!process.listeners('uncaughtException').length) throw e;
Error: socket hang up
at createHangUpError (http.js:1360:15)
at ServerResponse.OutgoingMessage._writeRaw (http.js:507:26)
at ServerResponse.OutgoingMessage._send (http.js:476:15)
at ServerResponse.OutgoingMessage.write (http.js:749:16)
at XHRPolling.doWrite (/node_modules/socket.io/lib/transports/xhr-polling.js:67:17)
at XHRPolling.HTTPPolling.write (/node_modules/socket.io/lib/transports/http-polling.js:132:8)
at XHRPolling.Transport.packet (/node_modules/socket.io/lib/transport.js:515:15)
at Object. (/node_modules/socket.io/lib/transports/http-polling.js:79:12)
at Timer.list.ontimeout (timers.js:101:19)


Seeing the same error with node v0.8.20. Probably due to this fix in node:

http: Raise hangup error on destroyed socket write (isaacs)

Happens when you reload a page on the browser.


Just tried with v0.8.19 and the exception does not happen.

@ereslibre ereslibre added a commit to ereslibre/socket.io that referenced this issue Feb 18, 2013
@ereslibre ereslibre Surround noop packet polling with try-catch. Since node.js version 0.…
…8.20 (http: Raise hangup error on destroyed socket write (isaacs)) a hangup

error is raised when trying to write on destroyed sockets.

fixes #1160

Looks like this issue was resolved for EtherPad with Node release 0.8.21


This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment