Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0b1
Issue ID
979679
Regression
Yes
.NET 4.6 Scripting runtime: Unity executable hangs when running tests in batchmode
To reproduce:
Run the attached project with the following command line
"<your path to Unity Editor>\Unity.exe" -projectPath "<your path to project>\RuntimeScriptingVersionBug" -batchmode -runTests
Unity never quits although it should after finishing everything
Not reproduced when switched to .NET 3.5.
Reproduced in 2018.1.0b1
Not reproduced in 2017.1.0a7
Comments (3)
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
- Errors are logged when importing an asset at a path with Firebase
- Entering too big of a number in 2D Renderer Lightmode Tags freezes the Editor
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
JoshPeterson
Apr 10, 2018 16:53
This has been corrected in 2018.1 as well. It should be fixed in the latest 2018.1 beta release.
chris_unity60
Apr 09, 2018 23:46
Any update on this? I'm hitting the same issue whether I use .NET 3.5 or .NET 4.6 on MacOS and Linux. Repros in Unity 2017.3.1f1 and Unity 2018.1.0b13. It prevents us from running unit tests on our CI server.
goldbug
Mar 27, 2018 18:19
What is taking so long? you have the fix, can't you just put it on a patch release? You keep releasing unity updates and this bug seems stuck in "fixed in future release".