[GR-62119] Remove AccessAdvisor assertions with data races. #10683
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.
In CI, we hit cases where these assertions tripped. Each call to
shouldIgnoreClass
is definitely preceded by a call toshouldIgnore
that returnedfalse
, so this was odd.AFAICT, the only non-final value used in the body of
shouldIgnore
is the "is live" check. My suspicion is that we receive a VMDeath event on a separate thread, set "is live" tofalse
, and then the second call toshouldIgnore
returnstrue
.We don't actually do any synchronization when the VM phase updates, which is likely a more fundamental problem with the agent. Rather than try to tackle that here, I propose to remove the assertions (I have manually checked that calls are preceded by
shouldIgnore
checks) to fix the transient errors.