RunImmediate should use RunSynchronously if called on UI thread #11805
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.
We added RunImmediate in #11788 and it gives much, much better debug stacks.
However we hadn't realised that in FSharp.Editor this was sometimes being called on the UI thread - notably for GoToDefinition for external sources. This results in a UI hang for this case. Running an async synchronously on the UI thread is not what we want. So we protect against that.
For this case we rename RunImmediate to RunImmediateExceptOnUI.
(RunImmediateExceptOnUI is now effectively the old F# 4.0 spec for RunSynchronously . This got changed in #11142 to check for isThreadPoolThread, which made our stacks originating from Roslyn background threads worse.)