JDK-8195690 : JNI GetObjectRefType doesn't handle NULL
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 11
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2018-01-18
  • Updated: 2020-09-01
  • Resolved: 2018-01-24
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 11
11 b01Fixed
Related Reports
Relates :  
JDK-8194312 - Support parallel and concurrent JNI global handle processing
Description
There are missing NULL checks in some JNIHandles functions.
The assertion gets hit on all platforms. Stack on Windows:
V  [jvm.dll+0xbb501d]  VMError::report_and_die+0x5d  (vmerror.cpp:1241)
V  [jvm.dll+0x5286f8]  report_vm_error+0x78  (debug.cpp:216)
V  [jvm.dll+0x9e4e0a]  OopStorage::allocation_status+0x4a  (oopstorage.cpp:611)
V  [jvm.dll+0x755c98]  JNIHandles::handle_type+0x48  (jnihandles.cpp:209)
V  [jvm.dll+0x72e987]  jni_GetObjectRefType+0x1c7  (jni.cpp:868)
Comments
Ran jck-runtime:vm/jni tests without any failures.
15-03-2018
Updated summary to better description. In a debug build we get the following assertion: assert(ptr != __null) failed: precondition with the backtrace quoted in the description.
22-01-2018
jck test ���vm/jni/GetObjectRefType/gort001/gort00103m1/gort00103m1.html���
18-01-2018
[~mdoerr] Is there a specific test that reproduces this failure mode?
18-01-2018