18.12.0.0

Need help?

Schedule a consultation with an Azul performance expert.

18.12.0.0

Release date: December 20, 2018

This release corresponds to the following OpenJDK versions:

Major Version	OpenJDK Version
8
11
13
15

What’s New

Support for Java SE 11.
A completely rewritten GC Log Analyser, GCLogAnalyzer2.jar, that enables faster loading, less memory usage, and JIT compilation activity graphs.
Support for JEP 254, the compact strings optimization, that helps reduce memory footprint and improve performance of string-intensive applications.

New command-line options or options with changed default values:
- ExitOnOutOfMemory
- CrashOnOutOfMemoryError
- GPGCNewGenConcurrentMarkFlushRetryLimit
- GPGCNewGenConcurrentMarkFlushRetryLimitAction
- UseSpecialArrayCopy
- UseModifiedThreadLocal
libc_hooks2 changed to libc_hooks3 for native launch with Zing.

Resolved Issues

Issue ID	Description
16227	With -XX:+UseC2 the JVM crashed in rorI_rReg_imm1 when using ojdbc8.jar.
15711	ZingMXBean metric PercentJavaHeapOccupiedAfterCollection always returns 100%.

Issue ID

Description

16227

With -XX:+UseC2 the JVM crashed in rorI_rReg_imm1 when using ojdbc8.jar.

15711

ZingMXBean metric PercentJavaHeapOccupiedAfterCollection always returns 100%.

Known Issues

Issue ID	Description
15789	In Java 11 testing, a rare ZVM 18.12 crash was observed when returning from the invocation of a MethodHandle routine. Analysis revealed the failure to be reproducible under rare circumstances in Java 8 with previous ZVM releases. Frequency of reproduction appears to be influenced by use of ReadyNow with Java 11. It is recommended that users of ReadyNow do not upgrade to Java 11 until this issue is resolved.

Issue ID

Description

15789

In Java 11 testing, a rare ZVM 18.12 crash was observed when returning from the invocation of a MethodHandle routine. Analysis revealed the failure to be reproducible under rare circumstances in Java 8 with previous ZVM releases. Frequency of reproduction appears to be influenced by use of ReadyNow with Java 11. It is recommended that users of ReadyNow do not upgrade to Java 11 until this issue is resolved.