Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2018.3.X
Votes
0
Found in
2018.2.3f1
2018.2.5f1
Issue ID
1073824
Regression
Yes
[Android] The Java.exe process that executed Gradle is not Terminated when a Build in Batch mode is completed
To reproduce:
1. Download attached project "AndroidTest.zip"
2. Open Command Prompt
3. Write this line "\path\to\Unity.exe" -batchMode -projectPath "\path\to\this\project" -quit -executeMethod Builder.Build -buildTarget Android and execute it
4. Open Task Manager, find there Windows Command Processor and expand it
5. Wait until Build is complete
6. Observe that after a build is complete, the Java.exe process that executed Gradle remains running
Notes:
- This process is holding on to several file handles (including the Unity log file) and consumes a lot of memory
- If you try to Build project in Unity Editor, there will also be the Java.exe process that executed Gradle running, but after you close Unity Editor, it will be terminated
Reproduced on Unity 2018.2.3f1, 2018.2.6f1 and 2018.3.0a11
Not reproduced on Unity 2018.1.9f2 and 2018.2.2f1 (c18cef34cbcd)
Regression on Unity 2018.2.3f1 (1431a7d2ced7)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit 'background-size' property is not fully animatable
- Moving the Scrollbar via clicking no longer works after the first-click when page size is too small
- Elements in UI Builder Viewport are displayed incorrectly when Editor UI Scaling is set to 125%
- Prefab referencing a script is not shown in the Search window's Project tab when using "Find References In Project"
- Scroll view sensitivity remains unchanged when modifying the "--unity-metrics-single_line-height" value
mobadu
Feb 19, 2020 15:41
Still the same issue on 2019.2.11f and 2019.2.19f