[release/9.0] Fix heap corruption issue in PriorityQueue.Remove #107603
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.
Backport of #107550 to release/9.0
/cc @eiriktsarpalis
Customer Impact
The newly added
PriorityQueue.Remove
method has bug which under certain circumstances can result in heap invariants not being preserved. In practice this means that elements can be dequeued out-of-order violating the guarantees of the collection.Regression
Testing
Added unit testing validating correctness for inputs where the issue is manifested.
Risk
Low. Makes a targeted change in production code adding an omitted order comparison.