Fix for a nullref thrown when PSES calls ForcePSEventHandling #1097
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.
In PowerShell Editor Services, we have a private contract with PSRL with a method called
ForcePSEventHandling
found in:Due to the multi-threaded nature of PSES, we are calling
ForcePSEventHanding
before the_forceEventWaitHandle
was initialized (which happens inDelayedOneTimeInitialize(
) thus causing a null reference exception.This PR moves the initialization to the field declaration which fixes the issue we were seeing (PSES crashing).
This should be low risk as this is only used by PSES and they are a private contract.