ci: skip ASan for GraalVM (shadow memory conflict)#590
Merged
Conversation
GraalVM pre-allocates fixed memory in 0x500000000000-0x52f000000000 which conflicts with ASan's required shadow range. No ASLR tuning resolves this (google/sanitizers#856). Skip asan+graal on both amd64 and aarch64. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This comment has been minimized.
This comment has been minimized.
![dd-octo-sts[bot]](https://avatars.githubusercontent.com/in/1157446?s=60&v=4){kind=small}
Contributor
CI Test ResultsRun: #27327237803 | Commit:
Status Overview
Legend: ✅ passed | ❌ failed | ⚪ skipped | 🚫 cancelled Summary: Total: 32 | Passed: 32 | Failed: 0 Updated: 2026-06-11 06:19:26 UTC |
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
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.
What does this PR do?:
Skip ASan runs when the JDK is GraalVM. Both amd64 and aarch64 test jobs are covered.
Motivation:
GraalVM pre-allocates fixed memory in
0x500000000000–0x52f000000000at JVM startup. This range conflicts with ASan's required shadow memory region[0x00007fff7000–0x10007fff7fff], causing ASan to abort with a shadow memory initialization failure before any test runs. The existingvm.mmap_rnd_bits=8/setarch --addr-no-randomizeASLR tuning does not help because GraalVM's pre-allocation is unconditional, not ASLR-driven. This is a known upstream incompatibility: google/sanitizers#856.Failing nightly run: https://github.com/DataDog/java-profiler/actions/runs/27253333727/job/80482463485
Additional Notes:
The existing
(j9|ibm)block setsMAX_ATTEMPTS=2(retry logic). The graal skip is different in kind — it exits cleanly withexit 0and a::notice::annotation, so the job shows green without masking real failures.How to test the change?:
The nightly sanitized workflow will exercise this path. The
graal+asanmatrix cell should now complete successfully (exit 0, notice annotation visible in the job log) instead of aborting with an ASan shadow memory error.No code change — CI workflow only; automated test not applicable.
For Datadog employees:
@DataDog/security-design-and-guidance.