Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Shenandoah and ZGC #12644

Closed
wants to merge 2 commits into from
Closed

Support Shenandoah and ZGC #12644

wants to merge 2 commits into from

Conversation

trustin
Copy link
Contributor

@trustin trustin commented Dec 7, 2020

Bazel currently refuses to start up when JVM is launched with -XX:+UseShenandoahGC or
-XX:+UseZGC. This can be easily fixed by making RetainedHeapLimiter recognize the
memory pool name Shenandoah and ZHeap.

Bazel currently refuses to start up when JVM is launched with `-XX:+UseShenandoahGC`.
This can be easily fixed by making `RetainedHeapLimiter` recognize the memory pool name
`Shenandoah`.
@google-cla google-cla bot added the cla: yes label Dec 7, 2020
@jin jin added the team-Rules-Java Issues for Java rules label Dec 7, 2020
@trustin trustin changed the title Support Shenandoah GC Support Shenandoah and ZGC Dec 7, 2020
apattidb pushed a commit to databricks/bazel that referenced this pull request Dec 8, 2020
Bazel currently refuses to start up when JVM is launched with `-XX:+UseShenandoahGC` or
`-XX:+UseZGC`. This can be easily fixed by making `RetainedHeapLimiter` recognize the
memory pool name `Shenandoah` and `ZHeap`.

Upstream: bazelbuild#12644
@bazel-io bazel-io closed this in f23aa21 Dec 8, 2020
@trustin trustin deleted the patch-1 branch December 9, 2020 04:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes team-Rules-Java Issues for Java rules
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants