Search Issue Tracker
By Design
Votes
0
Found in
2023.1.0a4
Issue ID
UUM-9868
Regression
Yes
Getting a null exception when catching awaited Task cancelation
Reproduction steps:
1. Open the user's attached project
2. Open Window > General > Test Runner
3. In the Test Runner window select PlayMode and click "Run All"
Expected result: The "TaskException_IsHandledSynchronously" test fails
Actual result: The "TaskException_IsHandledSynchronously" test is successful
Reproducible with: 2021.2.0a18, 2021.3.6f1, 2022.1.9f1, 2022.2.0b1, 2023.1.0a3
Not reproducible with: 2020.3.37f1, 2021.2.0a17
Reproducible with: Windows 10
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
This is actually a fix coming from a Mono update to align await behavior with CoreCLR. Any "await" statement that is not already completed have there continuation scheduled using the current execution context, even if the SetResult or SetException call raising completion happens from the same thread.
So in that case, the test check for the exception while the task has not ran to completion