Skip to content

Conversation

@graalvmbot
Copy link
Collaborator

In CI, we hit cases where these assertions tripped. Each call to shouldIgnoreClass is definitely preceded by a call to shouldIgnore that returned false, 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" to false, and then the second call to shouldIgnore returns true.

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.

@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Feb 13, 2025
@graalvmbot graalvmbot closed this Feb 14, 2025
@graalvmbot graalvmbot deleted the mdsouza/GR-62119-access-advisor-assertion branch February 14, 2025 01:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

OCA Verified All contributors have signed the Oracle Contributor Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants