Search Issue Tracker
Fixed
Fixed in 1.4.5
Votes
1
Found in [Package]
1.4.2
Issue ID
DSTR-1007
Regression
No
UnitySetUp does not fail when nested coroutines throw an exception
Reproduction steps:
1. Open the attached “Repro“ project
2. Open the Test Runner window (Window > General > Test Runner)
3. Select the “PlayMode” tab and run all tests by clicking the “Run All” button
4. Observe the Console
Expected result: Exception is thrown in the Console but the test doesn't fail and the Editor hangs
Actual result: Exception thrown in the Console fails the test and the Editor returns to its normal state
Reproducible with: 2021.3.33f1, 2022.3.16f1, 2023.2.4f1, 2023.3.0a19
Reproducible on: M1 MacOS 14.2
Not reproducible on: No other environment tested
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note (fix version 1.4.5):
Fixed an issue where UnitySetUp or UnityTearDown does not fail when nested coroutines throw an exception.