You are here:

Zing Virtual Machine Release Notes

Release date: July 31, 2020

Version 1.0

Changes made in Zing Virtual Machine 20.07.0.0 are summarized on this page.

What's New

Below is the list of new features and updates introduced in Zing Virtual Machine 20.07.0.0.

July 2020 CPU Release	ZVM 20.07.0.0 brings the associated JDK 7, JDK 8, and JDK 11 versions to July 2020 Critical Patch Update (CPU) security update levels and incorporates changes related to OpenJDK 7u271, OpenJDK 8u261, and OpenJDK 11.0.7.0.101 release contents. See Common Vulnerabilities and Exposures Fixes for the list of July 2020 security-only fixes.
Lock-Less JNI Protocol Enabled	The lock-less Java Native Interface (JNI) protocol is enabled by default in ZVM 20.07.0.0. See Using ZVM Command-Line Options for the `UseThreadStateNativeWrapperProtocol` option and details.
Performance Improvement	ZVM 20.07.0.0 introduces optimization in object allocation (internal `new_stub()` function) for improved performance in TLAB allocation intensive applications. The optimization is enabled by default.
Time To Safepoint Profiling Enhancement in Java Flight Recorder	Zing 20.07.0.0 provides support for profiling Time To Safepoint (TTSP) issues based on data about the Zing Virtual Machine events collected by the Java Flight Recorder (JFR). See Using TTSP Profiling for JFR Events for details.
Transport Layer Security Protocol Version 1.3 in Zing 8	Starting with ZVM 20.07.0.0, Zing 8 supports TLS 1.3 by default and follows the application programming interface (API) changes introduced by Maintenance Release 3 to the Java SE 8 specification. See Using Version 1.3 of Transport Layer Security (TLS) Protocol for more information.

The following table contains an issue resolved in the release of Zing Virtual Machine 20.07.0.0.

Bug ID	Description
ZVM-15833	Add additional logging of padding sizes.

The following table contains a known issue in the release of Zing Virtual Machine 20.07.0.0.

Bug ID	Description
ZVM-16112	Applications using `munlockall()` require `-XX:-UseThreadStateNativeWrapperProtocol` on the command line to avoid crash or inconsistency if the rare situation occurs that the application gets swapped out after the `munlockall()` invocation.

See Also

Last modified: July 31, 2020