JDK-8215399 : [JVMCI] release JNI handles in shared library properly
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 13
- Priority: P4
- Status: Closed
- Resolution: Duplicate
- Submitted: 2018-12-14
- Updated: 2019-04-29
- Resolved: 2019-04-29
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.
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 13 |
|---|
13Resolved  |
Related Reports
|
Blocks :
|
|
|
Duplicate :
|
Description
Interfacing with the JVMCI shared library uses JNI which means calls into the shared library from the VM that return object values will be holding onto a local JNI handle. To release this handle, the call needs to be in the scope of a JNI local handles frame that releases the local handles when the scope exits.
Comments
|