Reset SynchronizedBlock cache after each iteration #510
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ar out the object/Synchronized block cache. Added an end iteration callback registration to the TestingEngine constructor that will clear out the Monitor.SynchronizedBlock cache after each iteration to be sure no entries carry over across iterations for cases such as the max step bound being hit and all controlled operations being abruptly stopped.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When an iteration is stopped due to the maximum step bound being hit, all the controlled threads/operations are abruptly interrupted which can leave orphaned entries in the Monitor.SynchronizedBlock.Cache. When subsequent iterations try to run, they are all guaranteed to fail quickly because they will find instances of SynchronizedBlock in the cache from the previous runtime.
This fix is to make sure the cache is cleared after each iteration run.