TaskCompletionSource may hang an application when used with async/await. #84
+10
−12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please start with this article https://devblogs.microsoft.com/premier-developer/the-danger-of-taskcompletionsourcet-class/
It had bitten us several times in the past, so I analyzed the code and for all TCS-s that are used with async/await, added the TaskCreationOptions.RunContinuationsAsynchronously option.
No, I have not got into the problem yet with MTConnect.NET. But from the experience it will happen sooner or later.