On Tue, 2 Jun 2026 20:26:24 GMT, Chris Plummer <[email protected]> wrote:
> Most SA tests rely on the debuggee basically being idle and not doing things > like triggering a GC. Unfortunately this cannot be 100% guaranteed. One issue > is with LingeredApp.main(), which wakes up from sleep every second to touch > the lock file. This could generate a small amount of garbage which could > trigger a GC. This normally never happens, but we were seeing a case where it > did if CDS was disabled. Forcing a GC before the loop seems to fix the issue. > > Tested with svc CI testing in all tiers. Also ran SA tests a large number of > times with and without the fix, and it seems to be reliable. > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai). Marked as reviewed by ayang (Reviewer). ------------- PR Review: https://git.openjdk.org/jdk/pull/31355#pullrequestreview-4413523592
