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
- Sprites is not rendered in a SRP Batcher when Sprite Mask is removed after it was previously set
- Crash on MemoryProfiler::GetAllocationRoot when entering Play mode on a specific project
- Video Player preview is not shown when Inspector preview is converted to Floating Window
- Invalid signature package console message is not visible after package import when Console has 'Clear on Recompile' setting enabled
- Cannot interact with GameObjects in the Hierarchy window by using shortcuts or edit menu when selecting a GameObject in the Hierarchy with a “Select” window opened
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.