JDK-8289302 : Restore CriticalJNINatives
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 18,19
  • Priority: P3
  • Status: Resolved
  • Resolution: Won't Fix
  • Submitted: 2022-06-28
  • Updated: 2024-05-16
  • Resolved: 2022-09-30
Related Reports
Relates :  
JDK-8254693 - Add Panama feature to pass heap segments to native code
Relates :  
JDK-8258192 - Obsolete the CriticalJNINatives flag
Relates :  
JDK-8303210 - [linux, Windows] Make UseSystemMemoryBarrier available as product flag
Relates :  
JDK-8292591 - Experimentally add back barrier-less Java thread transitions
Description
Customer(s) have been using this internal feature for performance and removing it in JDK 18 without a replacement yet has been noted by a Java developer.

 See thread:
https://mail.openjdk.org/pipermail/hotspot-dev/2022-June/060945.html

And panama-dev thread:
https://mail.openjdk.org/pipermail/panama-dev/2022-June/017074.html

We'll work with customers to find an appropriate replacement in Panama but for now, this feature is important for Java customers and needs to be restored with the deprecation message.
Comments
Resolving this as WNF. We're providing some functionality to improve performance of native function calls, that we will support instead if helpful. See JDK-8292591.
30-09-2022
[~simonis] It has been closed as a duplicate of a closed JBS issue - which is far from ideal.
26-09-2022
@coleenp, can you please update this issue? The Status mentions that it is closed as duplicate, but I can't find which other issue it duplicates. I think this should probably just be reopened.
26-09-2022
This is a duplicate bug.
14-07-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk19/pull/90 Date: 2022-06-29 12:10:35 +0000
29-06-2022