Support Q - unhandled error events

[ORESoftware]

Hi all: looking for answers online for this one:

events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: This socket is closed.
    at Socket._writeGeneric (net.js:640:19)
    at Socket._write (net.js:694:8)
    at doWrite (_stream_writable.js:292:12)
    at writeOrBuffer (_stream_writable.js:278:5)
    at Socket.Writable.write (_stream_writable.js:207:11)
    at Socket.write (net.js:618:40)
    at process.<anonymous> (c:\Users\denman\WebstormProjects\suman\lib\handle-uncaught-exception.js:24:20)
    at emitOne (events.js:77:13)
    at process.emit (events.js:169:7)
    at process.startup.processFatal.process._fatalException (node.js:223:26)

I debugged through my code 20 times, I swore it was this then I swore it was that, but turns out no obvious part of my code is causing the error. I am on Windows, I don't believe the problem happens on OSX, tried on both, only happens on Windows, unfortunately, it's not clear at all where it originates from.

[fl0w]

Without some minimal reproduceable code It's very hard for anyone to guess why this occurs. But the error is thrown because you're trying to write to a socket that is closed.

If you're using a specific library, I'd personally try to isolate this, and check with library authors (because this looks like a user-land error, not node itself).

[cjihrig]

This isn't the right place for general support questions. Please move your questions to https://github.com/nodejs/help. If you discover an actual bug with Node, please report it here.

[ORESoftware]

@cjihrig np, noted thanks

[ORESoftware]

Well it appears to be a bug with Node, if only because Windows and OSX act differently with core code, it may because of fs-events from chokidar, but that's just a guess

[cjihrig]

If you think it might be a bug in Node core, please provide a runnable example that reproduces the problem without any external dependencies like fs-events.