Search Issue Tracker

Won't Fix

Votes

0

Found in

2021.3.9f1

2022.1.14f1

2022.2.0b7

2023.1.0a6

2023.2.0a1

Issue ID

UUM-14309

Regression

No

Unity processes aren't closed when running the "-quit" command line argument with Unity Accelerator enabled

--

-

Steps to reproduce:
1. Install Unity Accelerator
2. Open the attached project “IN-13628.zip“
3. Navigate to Edit > Preferences > Asset Pipeline
4. Input the IP address from Unity Accelerator and press “Check Connection” (connection has to be successful)
5. Navigate to Edit > Project Settings > Editor > Cache Server
6. Make sure that the IP address is the same as in Preferences plus HTTP Port
7. Change the Namespace prefix to something else than the default (e. g. “a“)
8. Run the “CustomerScript.ps1“ file using Windows PowerShell (change the project and Editor paths in the file)
9. Open Task Manager and observe the running processes under Windows PowerShell
10. Open \[project]/log_2021.txt file and scroll all the way down
11. Observe that the “Exiting batchmode successfully now\!“ line is present in the logs

Expected result: No Unity processes are running under the Windows PowerShell app
Actual result: Several Unity processes are present under the Windows PowerShell app

Reproducible with: 2021.3.9f1, 2022.1.14f1, 2022.2.0b7, 2023.1.0a6
Couldn’t test with: 2020.3.39f1 (the project does not open)

Reproducible on: Windows 10

Notes:
1. Unity version 2022.1.14f1 is inconsistent when reproducing this issue
2. When changing the Editor path in the “CustomerScript.ps1“ file make sure that it has no spaces
3. Look at the attached video (“Repro video.mp4“) for clarity

  1. Resolution Note:

    There are no fixes planned for this Bug

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.