Search Issue Tracker
Third Party Issue
Votes
0
Found in
2022.3.58f1
6000.0.38f1
6000.1.0b6
6000.2.0a3
Issue ID
UUM-97401
Regression
No
Task status is "WaitingForActivation" when awaiting a faulted task inside that task
Reproduction steps:
1. Open the attached “IN-92069” project
2. Execute the test (Tools > Run Test)
3. Observe the Console window
Expected result: “Task.Status” is “Faulted” and assertion is not printed
Actual result: “Task.Status” is “WaitingForActivation” and assertion is outputted as failed
Reproducible with: 2022.3.58f1, 6000.0.38f1, 6000.1.0b6, 6000.2.0a3
Reproducible on: Windows 10, Windows 11 (user)
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
- "Customize handled extensions" part in the External Tools settings tab is not aligned with other properties
- Editor Diagnostics foldouts do not open when clicked on the foldout title
- [UI Builder] Visual Elements are not placed at the mouse cursor position when Absolute Position Placement is enabled
- "Width" and "Height" text is misaligned with slider ends in Screen Match Mode Parameters section of Panel Settings Asset
- Editor does not quit when Editor is not in focus and any floating window is opened
Resolution Note:
The issue here is in user code:
```
var task = StartProcess();
Thread.Sleep(1000);
Debug.Log(task.Status); // WaitingForActivation
Debug.Assert(task.Status != TaskStatus.WaitingForActivation); // Assertion failed
```
The Thread.Sleep call here is blocking the main thread, making the await Task.Delay() call never resume. So Task1 is actually blocked before it can raise its exception.
The outmost task (the one generated by the async state machine as a continuation to the Task.Delay call) is thus in WaitingForActivation state as it is supposed to resume on main thread, but can't.