Windows: Check if all processes really exited and released resources #159
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.
The PR makes sure we're only listening to completion events for the
key
that we're interested in. This isn't much of an issue now but the new I/O manager for Windows will exclusively use I/O completion ports. Which means this method may mistakenly handle events it shouldn't have.Secondly it fixes a rare but annoying condition. When you receive a notification on the port that a process has terminated this does not mean that the resources of the process has been flushed.
Previously we were immediately unregister the process once we get the notification. However things like
hsc2hs
which rely on the child process having written a file then may get into a race condition. Control may return to the caller before the file has actually been written.Windows deals with this by returning an exit code
STILL_ACTIVE
which is to be interpreted as"process has exited but has not yet been cleaned up"
. If we get such an event we then block and wait for the OS to signal the handle and re-set the exit code.This fixes https://gitlab.haskell.org/ghc/ghc/issues/17108 and https://gitlab.haskell.org/ghc/ghc/issues/17249