Search Issue Tracker
Active
Votes
0
Found in [Package]
2017.3.0a1
2018.2.6f1
2018.3.0a1
2019.1.0a1
Issue ID
1112534
Regression
No
The `finally` block is not called in UnityTest if error message is logged
Steps to reproduce:
1. Download 1112534_repro.zip project
2. Run test in play mode
Expected results: Code in both "try" and "finally" blocks are called
Actual results: Code "finally" block isn't called
Reproduced with:2019.1.0a13, 2018.3.2f1, 2017.4.18f1
Example code:
[UnityTest]
public IEnumerator FinallyNotCalled()
{
try
{
Debug.LogError("a");
yield return null;
Debug.Log("b");
}
finally
{
Debug.Log("finally");
}
}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment