Crash on downloading plugin about locker HOT 3 CLOSED

The exception takes down the main locker process but leaves other node processes running. Restarting locker fails with:

jamie@jamie-aspire:~/Locker$ node locker.js
[01:27:21][Locker] Installing c638801c4fb3759985c239f9da53c0c4
[01:27:21][Locker] Spawned dashboard pid: 7169
[01:27:21][Locker] locker running at http://localhost:8042/
[01:27:21][Locker] id keys loaded
[01:27:22][Locker] dashboard stdout: http://localhost:18042/

[01:27:22][Locker] Error dashboard:

[01:27:22][Locker] Error dashboard: node.js:116

[01:27:22][Locker] Error dashboard: throw e; // process.nextTick error, or 'error' event on first tick

[01:27:22][Locker] Error dashboard: ^

[01:27:22][Locker] Error dashboard: Error: EADDRINUSE, Address already in use
at HTTPServer._doListen (net.js:1062:5)
at net.js:1033:14
at Object.lookup (dns.js:132:45)
at HTTPServer.listen (net.js:1027:20)
at Object. (/home/jamie/Locker/Ops/Dashboard/dashboard.js:188:5)
at Module._compile (module.js:383:26)
at Object..js (module.js:389:10)
at Module.load (module.js:315:31)
at Function._load (module.js:276:12)
at Array. (module.js:402:10)

[01:27:22][Locker] dashboard died with code 1

from locker.

So the comment issue is a more annoying one due to the crash in the core and needing to find a way to cleanup the children processes in that case. We'll deal with that later, and could you spin it off as a new issue?

The plugin issue is proving to be rather nasty. The first part of the issue had to do with the way the file was sent causing a redirect. This redirect handler would send headers, but then after the successful redirect more headers were attempted to be sent. Once that issue was resolved the plugin is now not loading by Chrome. Still under investigation.

from locker.

This code has been deprecated.

from locker.