JDK-8251923 : "Invalid JNI handle" assertion failure in JVMCICompiler::force_comp_at_level_simple()
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 11,15,16
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- CPU: aarch64
- Submitted: 2020-08-18
- Updated: 2024-11-20
- Resolved: 2020-08-20
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 11 | JDK 16 |
|---|---|
| 11.0.11-oracleFixed | 16 b13Fixed  |
Description
See the attached crash dump. This happens occasionally on some AArch64 machines when using Graal. There seems to be a race between JVMCI initialisation and a compiler thread querying it via JVMCICompiler::force_comp_at_level_simple().
Comments
|