Fix scheduler suspend edge case assertion #2641
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.
Prior to this commit, it was possible for a scheduler thread to
suspend even though it wasn't appropriate to do so because
another scheduler thread resumed prior to the lock being
acquired. This would result in incorrect behavior in the
release build and an assertion in the debug build.
See the following link for an example of the assertion being
triggered: https://circleci.com/gh/ponylang/ponyc/3809?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
This commit fixes the issue by not suspending if the schduler
count changed because another thread resumed.