JDK-8258192 : Obsolete the CriticalJNINatives flag
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 17
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2020-12-14
  • Updated: 2024-02-06
  • Resolved: 2021-11-12
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 18
18 b24Fixed
Related Reports
Relates :  
JDK-8233343 - Deprecate -XX:+CriticalJNINatives flag which implements JavaCritical native functions
Relates :  
JDK-8289302 - Restore CriticalJNINatives
Sub Tasks
JDK-8267691 :  
Change table to obsolete CriticalJNINatives in JDK 18, not 17 - Resolved
Description
The CriticalJNINatives flag was deprecated in JDK 16 and marked for obsoletion in JDK 17 (see JDK-8233343). However, it was deprecated under the premise that an alternative will be available via Project Panama. If the alternative is available then we should obsolete this flag in 17 as planned, else we should update the flag table to defer the obsoletion to a later release.
Comments
Changeset: 0d2980cd Author: Coleen Phillimore <coleenp@openjdk.org> Date: 2021-11-12 17:03:33 +0000 URL: https://git.openjdk.java.net/jdk/commit/0d2980cdd1486b0689a71fc107a1d4c100bd3025
12-11-2021
I don't think we should obsolete this flag yet. Panama does not yet have the functionality to decay an object array through a native function JDK-8254693, although it's unclear if anyone used this aside from solaris JDK internal code. Panama is still an early access feature in JDK 17, so we should wait for JDK 18 to obsolete it.
24-05-2021