On Fri, 28 Jan 2022 04:27:18 GMT, Chris Plummer <cjplum...@openjdk.org> wrote:
> When using -Xcomp, the liveness of some objects the test allocates is more > precisely known, allowing the objects to be collected before the test > expects. This became an issue in the loom repo because it has changes that > result in a full GC when the codecache is swept. This is fixed by using > statics to reference the objects. Also, if a GC does happen, this seems to > get rid of the Survivor region, so the test was updated to no longer check > for it. > > I'm choosing to fix this in the jdk repo rather than the loom repo since it > is a latent bug that theoretically could occur even without the loom changes, > and also to help reduce the amount of changes to be reviewed when loom is > integrated into jdk. This pull request has now been integrated. Changeset: 4532c3a1 Author: Chris Plummer <cjplum...@openjdk.org> URL: https://git.openjdk.java.net/jdk/commit/4532c3a1639af0b4ff8c4f42c3796fa73ca5be83 Stats: 6 lines in 2 files changed: 3 ins; 1 del; 2 mod 8280554: resourcehogs/serviceability/sa/ClhsdbRegionDetailsScanOopsForG1.java can fail if GC is triggered Reviewed-by: alanb, amenkov, lmesnik ------------- PR: https://git.openjdk.java.net/jdk/pull/7257
