fix(test): forkEvery for asan Test task to bound cumulative heap growth - #632
Merged
Merged
Conversation
The ASAN test JVM is pinned to -Xmx512m to keep the heap below ASan's shadow-memory region (ASLR constraint). Without forkEvery, Gradle reuses a single JVM for the entire ddprof-test:testAsan suite, and per-test allocations (JFR recordings, JMC object models) accumulate across ~100+ test classes until the shared heap OOMs late in the run, even though every individual test passes. Restart the JVM every 25 classes to bound cumulative growth. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
![dd-octo-sts[bot]](https://avatars.githubusercontent.com/in/1157446?s=60&v=4){kind=small}
Contributor
CI Test ResultsRun: #34249245579 | Commit:
Summary: Total: 0 | Passed: 0 | Failed: 0 Updated: 2026-09-08 16:35:31 UTC |
1 of 2 tasks
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
2 participants
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.
Summary
test-linux-glibc-aarch64 (25, asan)failed withJava heap spacein run https://github.com/DataDog/java-profiler/actions/runs/28658114523/job/85000253879, even though every individual test in the run passed.ddprof-test:testAsanhas noforkEvery, so Gradle reuses a single forked JVM for the entire ~100+ class suite. That JVM is pinned to-Xmx512m(seeConfigurationPresets.kt) to keep the heap below ASan's shadow-memory mapping, an ASLR workaround that can't simply be raised. Per-test allocations (JFR recordings, JMC object models) accumulate across the whole suite until the shared heap runs out, even though no single test is at fault — a similar single-test instance of this was just fixed in fix(test): reduce ASAN wall-clock rate in BoundMethodHandleProfilerTest to avoid OOM #630 forBoundMethodHandleProfilerTest, but this run already included that fix and still OOM'd later in the suite.forkEvery(25)on theasanTesttask so the JVM restarts periodically and cumulative heap growth is bounded.Test plan
pre-release-tests / test-linux-glibc-aarch64 (25, asan)in CI and confirm it completes without theJava heap spacefailure.🤖 Generated with Claude Code