Search Issue Tracker

Fixed

Fixed in 3.5.1-beta.1

Votes

18

Found in [Package]

3.4

Issue ID

HUBX-850

Regression

No

Hub crashes with "Timeout! Cannot connect to Licensing Client within 60000ms" when opening it

Package: Hub

-

Reproduction steps:
1. Open the Hub
2. Observe crash

Reproducible with: 3.4.0, 3.4.1, 3.4.2

Reproducible on: Windows 10, MacOS

Note: Not reproduced by CQA

Full error:
ConnectionLost: Timeout! Cannot connect to Licensing Client within 60000ms
at IpcError.fromType (C:\Program Files\Unity Hub\resources\app.asar\node_modules@licensing\licensing-sdk\lib\core\ipc\licensingIpc.js:51:16)
at LicensingIpc.waitForConnection (C:\Program Files\Unity Hub\resources\app.asar\node_modules@licensing\licensing-sdk\lib\core\ipc\licensingIpc.js:118:152)
at LicensingSdk.getMachineId (C:\Program Files\Unity Hub\resources\app.asar\node_modules@licensing\licensing-sdk\lib\core\licensingSdk.js:68:37)
at LicensingSdk.<anonymous> (C:\Program Files\Unity Hub\resources\app.asar\build\main\services\licenseService\licensingSdk.js:118:86)
at Generator.next (<anonymous>)
at C:\Program Files\Unity Hub\resources\app.asar\build\main\services\licenseService\licensingSdk.js:31:71
at new Promise (<anonymous>)
at __awaiter (C:\Program Files\Unity Hub\resources\app.asar\build\main\services\licenseService\licensingSdk.js:27:12)
at LicensingSdk.getMachineId (C:\Program Files\Unity Hub\resources\app.asar\build\main\services\licenseService\licensingSdk.js:117:16)
at CloudAnalytics.<anonymous> (C:\Program Files\Unity Hub\resources\app.asar\build\main\services\cloudAnalytics\cloudAnalytics.js:93:56)

Comments (4)

  1. psynusoidal

    Oct 25, 2023 07:47

    This has regressed in 3.6.0.

  2. jdanek_unity

    May 11, 2023 06:50

    My error message also included this line

    Too many open files - Failed to initialize inotify: the user limit on the total number of inotify instances has been reached.

    I fixed this by following the inotify advice at https://stackoverflow.com/a/38486048/1047788

    That is, use

    $ cat /proc/sys/fs/inotify/max_user_instances

    to see how many inotify instances is permitted, and (most likely find out that it is 127)

    Than, use

    $ echo 256 | sudo tee /proc/sys/fs/inotify/max_user_instances

    to temporarily (until next reboot) increase that to 256, and try running unity now. It should work.

    Now make the change permanent by putting the following line into /etc/sysctl.conf

    fs.inotify.max_user_instances = 256

  3. mlhornbo

    Feb 19, 2023 03:57

    This is making Unity entirely unusable recently. Hope it is fixed quickly.

  4. zpunorm22

    Dec 28, 2022 19:09

    Also reproducible on Linux (Ubuntu 22.04) as well

Add comment

Log in to post comment