worker: fix deadlock when calling terminate from exit handler#22073
Uh oh!
There was an error while loading. Please reload this page.
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.
Just before we call the
'exit'handlers of a Worker, we drainthe public port’s message queue to ensure proper ordering.
Previously, we held the Worker’s
mutex_during theexit handler call, so calling
terminate()on the workercould lead to a deadlock if called from one of those message
handlers.
This fixes flakiness in the
parallel/test-worker-dns-terminatetest.Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes