Search Issue Tracker
Third Party Issue
Votes
0
Found in
2019.4
2020.3
2021.2
2021.2.5f1
2022.1
2022.2
Issue ID
1411509
Regression
No
Coroutines fail to catch exceptions that are located in the nested functions
Reproduction steps:
1. Open the user's attached "1197069_CoroutineException.zip" project
2. Open the "SampleScene" Scene
3. Enter the Play mode
4. Observe the Console window
Expected result: All exceptions are caught. 3 error messages and 3 regular messages appear
Actual result: The exception in the nested function is not caught. 3 error messages and 2 regular messages appear
Reproducible with: 2019.4.37f1, 2020.3.32f1, 2021.2.16f1, 2022.1.0b13, 2022.2.0a9
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note:
This is actually expected: the CoroutineRunner only captures the outermost iterator: on the failing case, the yielded enumerator.Current value is the IEnumerator of the sub function. The coroutine system thus iterates on it without getting trough the wrapper that is supposed to capture exceptions.
At line #69, the code should check if the return value is itself an IEnumerator and treat this case accordingly (probably by nesting wrapping it into a recursive call to CoroutineRunner.