Details
-
Bug
-
Resolution: Fixed
-
P4
-
13
-
b18
Description
The InstanceKlass' _method_ordering is not set during CDS dynamic dump time. This results in the following assert if JDWP option is used during runtime and a debugger is attached to the suspended java process.
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (open/src/hotspot/share/oops/instanceKlass.cpp:3615), pid=32154, tid=32155
# guarantee(length == methods()->length()) failed: invalid method ordering length
To reproduce:
1. Insert the following JDWP option in the runtime command line with a CDS dynamic archive:
-Xrunjdwp:transport=dt_socket,server=y,address=8888,suspend=y
2. Attach a debugger to the java process, e.g.
jdb -attach 8888
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (open/src/hotspot/share/oops/instanceKlass.cpp:3615), pid=32154, tid=32155
# guarantee(length == methods()->length()) failed: invalid method ordering length
To reproduce:
1. Insert the following JDWP option in the runtime command line with a CDS dynamic archive:
-Xrunjdwp:transport=dt_socket,server=y,address=8888,suspend=y
2. Attach a debugger to the java process, e.g.
jdb -attach 8888
Attachments
Issue Links
- relates to
-
JDK-8232030 HelloDynamic.java fails with latest Graal
-
- Resolved
-
-
JDK-8207812 Implement Dynamic CDS Archive
-
- Resolved
-