Search Issue Tracker
Fixed in 1.1.13
Votes
0
Found in [Package]
1.1.0
Issue ID
1213958
Regression
No
Test runs indefinitely and Editor crashes after running the test that reads/writes code that contains interfaces
How to reproduce:
1. Open the attached project "1213958.zip" and open Test Runner window
2. In the Test Runner window click Run All (at least 3 times, more information in the notes)
3. Observe the Unity Editor
Expected result: The test would fail due to a null exception, just like when running the test for the first time
Actual result: The test repeats indefinitely, Unity Editor becomes unusable, cannot cancel the Test Runner, forcing the Unity Editor to close leads to crash
Reproducible with: Test Framework 1.1.0 (2019.2.0a10, 2019.2.20f1), Test Framework 1.1.9 (2019.2.20f1, 2019.3.0f6), Test Framework 1.1.11 (2019.2.20f1,2019.3.0f6, 2020.1.0a22)
Could not test with: 2017.4.36f1, 2018.4.16f1, Test Framework 1.0.18 (2019.2.0a10, 2019.2.20f1) (the Script doesn't compile, due to differences of access modifiers of certain functions and missing references)
Notes:
-The issue behavior is unstable, sometimes it requires running the test only once to reproduce
-Not always the Crash Bug Reporter window pops up when Unity Editor crashes after forcing it to close
-Crashes without stacktrace on 2019.3
-Not reproducible on Mac
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note (fix version 1.1.13):
Fixed in 2019.2.0a10 with package Test Framework 1.1.13
Resolution Note (fix version 1.1.13):
Fixed in: 2019.3.6f1 with package Test Framework 1.1.13
Resolution Note (fix version 1.1.13):
Fixed in 2020.1.0b2 with package Test Framework 1.1.13