Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.2.X
Votes
0
Found in
2018.3.0a1
2018.4.1f1
2018.4.3f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1169988
Regression
Yes
Unity Editor crashes in dispatch_release when running Tests in Batch Mode
When changing the path of an Assembly Definition that is referenced by another Assembly Definition without opening Unity, and running Tests in Batch Mode, Unity Crashes
To reproduce:
1. Download attached "TestCrash.zip" project and extract it
2. Open TestCrash folder and change the Unity Path in the repo.sh script with the path where is Unity located on the Machine
3. Run repro.sh in the project root
4. Wait until Tests finishes
Expected results: The Project is compiled and the Tests are executed
Actual results: Unity crashes after logging "Scripts had compilation errors"
Notes:
- The repro.sh script does the following:
Runs Play mode Tests, which causes the Library to be Built
Renames the "Dependency" folder in Assets by "DependencyRenamed"
Runs Play mode Tests again, which crashes
- Editor.log and Crash details are shared in the Comments section
- It seems that this issue is fixed on Unity 2019.3.0a4_7368acd360f4
Reproduced on Unity 2018.3.0a1, 2018.3.14f1, 2018.4.4f1, 2019.1.11f1, 2019.2.0b10 and 2019.3.0a3
Not reproduced on Unity 2018.2.21f1, 2019.3.0a4 and 2019.3.0a10
Regression on Unity 2018.3.0a1
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (fix version 2019.3):
This is fixed in the latest 2019.3 builds and will be backported to 2019.2 and 2018.4.