Use DispatcherTaskScheduler instead of TaskScheduler.FromCurrentSynchronizationContext #17825
+51
−6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
maxkatz6
added
bug
os-browser
backport-candidate-11.2.x
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does the pull request do?
Due to
TaskScheduler.FromCurrentSynchronizationContextbeing unreliable on browser workloads, it's safer to explicitly provide dispatcher-based scheduler implementation.Also, @kekekeks what exactly should be done to ensure correct dispatcher priority? I could read current sync context and check for AvaloniaSynchronizationContext.Priority, if that's what you meant.
Fixed issues
This issue was reported couple of times in telegram chats.