diff options
| author | Stephen Toub <stoub@microsoft.com> | 2019-07-28 20:15:33 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-07-28 20:15:33 -0400 |
| commit | ac25be694a5385a6a1496db40de932df0689b742 (patch) | |
| tree | 799f7ca261363d5fdc4b7a36b2804112c732dcaa /dir.common.props | |
| parent | 3d4806e5bfc512128ed710e287ec7df141ce702b (diff) | |
| download | coreclr-ac25be694a5385a6a1496db40de932df0689b742.tar.gz coreclr-ac25be694a5385a6a1496db40de932df0689b742.tar.bz2 coreclr-ac25be694a5385a6a1496db40de932df0689b742.zip | |
Fix use of AddTo/RemoveFromActiveTasks in async methods (#25915)
When we rewrote the async methods implementation with AsyncStateMachineBox, we neglected to call AddToActiveTasks if the debugger is paying attention to tasks. This hasn't mattered as the debugger's support for Tasks hasn't worked for other reasons in .NET Core, but there is now a renewed focus on it, and this is preventing some of that support from working.
This change is a minimal fix to ensure that we're adding the state machine box task when it's created and removing it when it completes. Post-3.0, we should look at overhauling this, e.g. to clean up a lot of this logging and tracking that's done, to use a weak table in order to avoid keeping task objects alive artificially if they're dropped without completing by the developer code, etc.
This only affects when the debugger is attached, as the s_asyncDebuggingEnabled field is only ever set by the debugger.
Diffstat (limited to 'dir.common.props')
0 files changed, 0 insertions, 0 deletions