Search Issue Tracker
Fixed in 5.3.9
Votes
0
Found in
5.3.4p4
Issue ID
790610
Regression
Yes
Unity is not responding when trying to quit in headless mode
To reproduce:
1. Download attached project
2. In the terminal run command: "/Applications/Unity5.3.4p4/Unity.app/Contents/MacOS/Unity -projectPath "/Users/laurynas/Downloads/case_790610-client" -quit -batchmode -logFile "/Users/laurynas/Library/Logs/Unity/Editor_Core.log" -executeMethod DataValidator.JiraValidateAll"
Expected behavior: Unity should quit after method execution
Actual behavior: Unity gets to "application not responding" state when trying to quit
Regression from 5.2 to 5.3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment