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
- Tooltip messages should be presented in human language not in code strings
- [Linux] Editor doesn’t auto reload when an Asset is imported or a Script is changed
- MouseDownEvent is triggered when changing from Scene view to Game view
- "GlobalObjectIdentifierToObjectSlow" returns Null when retrieving "GlobalObjectId" from GameObject inside a Prefab
- Shader is invisible in the Build when using BiRP on Meta Quest 2
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.