Fix can't resume a running fiber
#14128
Merged
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 changes in #14098 require that the fiber be associated to a thread once, instead of doing it on every swapcontext, yet enqueueing the fiber didn't do it while associating the fiber to a thread, which led to further enqueues to associate the fiber to any other thread, in which case a thread B was trying to resume a fiber that was still running on thread A (it didn't swap context, yet).
closes #14124