Search Issue Tracker
Fixed
Votes
0
Found in
2018.4
2018.4.30f1
Issue ID
1297000
Regression
No
[Windows] Editor doesn't exit after making a build in Batch-mode when using a "quit" parameter and logging to file
How to reproduce:
1. Download and extract the attached project "case_1297000-Project.zip"
2. Open up a command prompt window
3. Write the following command: <Path to Unity>\Unity.exe -quit -batchMode -buildTarget WebGL -projectPath <Path to Project>
-executeMethod "BuildScript.BuildRelease" -silent-crashes -logFile <Path to Output>
4. Wait for the build process to finish
5. Open up the outputted log file
6. Inspect the end of the log
Expected result: Batch mode quit successfully
Actual result: Editor doesn't quit
Reproducible with: 2018.4.30f1
Not reproducible with: 2019.1.0a1, 2019.4.18f1, 2020.2.2f1, 2021.1.0b2, 2021.2.0a2
Note: Not reproducible on Mac
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note:
Fixed in Unity 2019.1.0a1 and above