Search Unity

  1. Unity 2019.2 is now released.
    Dismiss Notice

[Bug] Unity Hub Crashes on startup after creating 1 new project.

Discussion in 'Unity Hub' started by wayneglows, Feb 9, 2018.

  1. wayneglows

    wayneglows

    Joined:
    Mar 12, 2013
    Posts:
    14
    Capture.PNG

    1. Installed Unity Hub
    2. Used it to download Beta 2018.1.0b6
    3. Created a new project
    4. Project launched fine, Unity Hub immediately crashed, and now crashes each time I start it.
    5. The only available options are to restart (which launches and crashes it again) or Quit.

    I believe the culprit is this in the log file, (I can post or send the entire log file if there is a bug tracker for Hub) -

    {"moduleName":"App","level":"error","message":"A JavaScript error occurred in the main process\nUncaught Exception:\nError: listen EADDRINUSE :::39000\n at Object.exports._errnoException (util.js:1050:11)\n at exports._exceptionWithHostPort (util.js:1073:20)\n at Server.setupListenHandle [as _listen2] (net.js:1263:14)\n at listenInCluster (net.js:1304:12)\n at Server.listen (net.js:1402:7)\n at Function.listen (C:\\Program Files\\Unity Hub\\resources\\app.asar\\node_modules\\connect\\index.js:217:24)\n at SwaggerConnect.create (C:\\Program Files\\Unity Hub\\resources\\app.asar\\src\\services\\localREST\\hubRestService.js:38:31)\n at C:\\Program Files\\Unity Hub\\resources\\app.asar\\node_modules\\swagger-connect\\lib\\index.js:32:5\n at C:\\Program Files\\Unity Hub\\resources\\app.asar\\node_modules\\swagger-node-runner\\index.js:179:5\n at C:\\Program Files\\Unity Hub\\resources\\app.asar\\node_modules\\swagger-tools\\index.js:84:7\n at cbWrapper (C:\\Program Files\\Unity Hub\\resources\\app.asar\\node_modules\\swagger-tools\\lib\\specs.js:1035:5)\n at validateSwagger2_0 (C:\\Program Files\\Unity Hub\\resources\\app.asar\\node_modules\\swagger-tools\\lib\\specs.js:1030:3)\n at validateSemantically (C:\\Program Files\\Unity Hub\\resources\\app.asar\\node_modules\\swagger-tools\\lib\\specs.js:1040:5)\n at C:\\Program Files\\Unity Hub\\resources\\app.asar\\node_modules\\swagger-tools\\lib\\specs.js:1233:7\n at C:\\Program Files\\Unity Hub\\resources\\app.asar\\node_modules\\swagger-tools\\lib\\specs.js:1073:29\n at C:\\Program Files\\Unity Hub\\resources\\app.asar\\node_modules\\swagger-tools\\lib\\specs.js:719:12","timestamp":"2018-02-09T12:05:57.126Z"}
     
  2. wayneglows

    wayneglows

    Joined:
    Mar 12, 2013
    Posts:
    14
    Another issue with this bug has surfaced. The editor skin in Unity is now locked on Personal and unable to be changed. When I try to log out and back into my account, the editor throws an error in the console. I assume this means it is trying to talk to the crashed Unity Hub and obtain my account information.

    HUB window show request failed, Reason: The requested URL returned error: 500 Internal Server Error (500).
     
  3. afshinity

    afshinity

    Unity Technologies

    Joined:
    Jul 31, 2017
    Posts:
    331
    Hi there,

    I am sorry about your experience.

    Quitting the hub, can you check if the hub is still running in your task manager. From the logs, it looks like another instance of the hub (or another application listening on port 39000) is running in your computer.

    Regarding the editor console error, as you said it is because editor expecting to see hub, and it cannot. If you quit the hub, the editor should be able to fall back to its built-in launcher.
     
  4. wayneglows

    wayneglows

    Joined:
    Mar 12, 2013
    Posts:
    14
    I believe you are right on this. It looks like I had another copy of the HUB running on another Windows 10 account logged into the same computer. Thank you.
     
  5. afshinity

    afshinity

    Unity Technologies

    Joined:
    Jul 31, 2017
    Posts:
    331
    Yes, that's a known issue. We will work on a better solution to avoid port conflicts