Search Issue Tracker
Active
Votes
0
Found in [Package]
3.15.1
Issue ID
HUBX-1556
Regression
Yes
Performing Headless Editor or Module installs leaves ghost processes
Steps to reproduce:
1. Quit Unity Hub (Check task manager to ensure there are no active Hub Processes)
2. Open the CMD window
3. Perform a headless Editor version or Module install. For example - "C:\Program Files\Unity Hub\Unity Hub.exe" – --headless install-modules --version 6000.0.61f1 -m linux-mono
4. Wait for the process to finish
5. Try opening Unity Hub. Either via the CMD with "C:\Program Files\Unity Hub\Unity Hub.exe" or via shortcut
Expected result: Hub does not leave any ghost processes after a headless install operation, allowing the window to open
Actual result: The Hub window does not open due to leftover processes
Reproducible with Hub: 3.15.1
Not reproducible with Hub: 3.14.3
Reproducible on: Windows 10/11
Notes:
Hub leaves 4 processes after a headless install operation. Manually ending them can be used as a workaround
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Video does not play in macOS build when built app is placed in a path with a space in it on a specific project
- Crash on AuxWindowManager::OnGotFocus when trying to maximize a tab while Visual Effect Graph window is open
- “NullReferenceException: Object reference not set to an instance of an object” error is thrown when
- [Metal] Game freezes after command buffer Timeout error
- Addressables Report window UI is broken when opening via Build > New Build > Default Build Script
Add comment