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.

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

Remove call to Application.Current.Dispatcher.CheckAccess() - seems ther... #465

Merged

Conversation

amaitland
Copy link
Member

Remove call to Application.Current.Dispatcher.CheckAccess() - seems there's a null point happening on a rare instance when Application.Current.Dispatcher is null

Rely on parent calling code to execute on the correct thread (which it was already executing on the UI Thread)

…here's a null point happening on a rare instance when Application.Current.Dispatcher is null

Rely on parent calling code to execute on the correct thread (which it was already executing on the UI Thread)
@amaitland
Copy link
Member Author

When hosting the WPF Control under WinForms Application.Current also appears to be null

@amaitland
Copy link
Member Author

Issue #421 also relates to this (even though it's closed)

amaitland added a commit that referenced this pull request Sep 11, 2014
Remove call to Application.Current.Dispatcher.CheckAccess() - Fix null pointer when Application.Current is null
@amaitland amaitland merged commit 7ee3e85 into cefsharp:master Sep 11, 2014
@amaitland amaitland deleted the bug-fix/dispatcher-null-pointer branch September 11, 2014 03:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant