fix(core): make forked-process-task-runner robust to closed processes #14289
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.
Ensure that processes that have ended are no longer in the set of processes. Further, ensure the processes are connected before sending them messages.
Current Behavior
forked-process-task-runner never removes processes from
this.processes
. As such, if you send the task-runner process messages after one of the processes has exited, it throws errors like these:Expected Behavior
forked-process-task-runner should be resilient to this
Related Issue(s)
Fixes #