Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

5.0.1 throws invalid thread access on WPF main thread #2026

Closed
nirinchev opened this issue Sep 14, 2020 · 0 comments · Fixed by #2027
Closed

5.0.1 throws invalid thread access on WPF main thread #2026

nirinchev opened this issue Sep 14, 2020 · 0 comments · Fixed by #2027
Assignees
@nirinchev

Comments

@nirinchev
Copy link
Member

nirinchev commented Sep 14, 2020 •
edited by sync-by-unito bot
Loading

Seems like WPF's DispatcherSynchronizationContext returns a new instance on every callback instead of reusing the original one. This means that our referential equality check that detects if two SynchronizationContexts are the same doesn't work.
@nirinchev nirinchev mentioned this issue Sep 14, 2020
Merged
2 tasks
@nirinchev nirinchev self-assigned this Sep 14, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@nirinchev nirinchev

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Special-case DispatcherSynchronizationContext realm/realm-dotnet
1 participant
@nirinchev