Search Issue Tracker
Won't Fix
Votes
21
Found in
2017.2.0f3
Issue ID
958803
Regression
Yes
[macOS] Unity freezes and never exits when running Test Runner from Command Line
To reproduce:
1. Open Terminal window
2. Download user's project and unzip it
3. Launch Test Runner by using this command:
/(path to the folder with Unity's installation)/Unity.app/Contents/MacOS/Unity -projectPath (path to the folder with user's project) -batchmode -runTests -testPlatform editmode -logFile (enter path where log file should be saved)
Expected result: After running a test Unity should close itself (terminate).
Actual result: Unity freezes and you have to Force Quit it.
Reproduced with: 5.6.3p4, 2017.1.2p1, 2017.2.0f3, 2017.3.0b4, 2018.1.0a1
Not reproducible with: 5.5.5p1
Won't fix because we don't support static test methods.
Comments (12)
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
- A memory leak occurs with massive terrain when camera position changes occur.
- No valid hits are returned when using RaycastCommand
- Camera is not overlooking the main Scene in Scene View in the HDRP Sample Template
- TextShadow properties are not applied when displayed in a custom MenuItem Window
- Memory leak occurs when focused on Player while using Direct3D12
Tappsunity18
Jan 24, 2018 12:52
Any news on this? Same happening here on windows and unity 2017.3
Evgeny-Eliseev
Dec 18, 2017 07:43
What version future release means? :)
CapeGuyBen
Dec 12, 2017 14:15
This issue is not reproducible with Unity 5.6.3f1 so my projects are currently stuck on that version as upgrading means that all continuous integration tests fail (due to timeout). Also, as a Unity upgrade of the projects is required to work with macOS High Sierra, this issue is also currently blocking an OS upgrade.