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

Unity Engine
1

3385906--265994--Capture.PNG
3385906--265994--Capture.PNG1007×583 25.1 KB

  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

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

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

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

Yes, that’s a known issue. We will work on a better solution to avoid port conflicts

6

this happens for me but in a different instance. Whenever i run 2021 (beta 4), whenever it searches for templates, (2d, 3d, etc.), it will find like 4-5 templates and then freeze, where windows will say “Application not responding, close window or wait for program to respond.” I understand it is a beta and is prone to this, just hoping it gets fixed

7

This is still the fix. I had a log error report after having an infinite loop #rip sleepy coding. This morning I had 3 Unity Processes running in the background. Closed them waited a couple of secs and it started right up.