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
- NullReferenceException error is thrown when pinging the "Initial Scene" in the Play Mode Scenarios window
- "MaxRpcAgeFrames" NetCode RPC warning is logged when entering Play Mode in the Multiplayer FPS template
- "BatchRendererGroup.OnPerformCulling" is not called during Scene view picking when "HandleUtility.PickGameObject" is passed a non-empty filter
- Crash on RemovedMaskedCurve when opening a project with specific animations
- The sidebar reopens when Unity Hub is started when Unity Hub was closed with the sidebar closed
Add comment