Eclipse OpenJ9: A Java Virtual Machine for OpenJDK that's optimized for small footprint, fast start-up, and high throughput. Builds on Eclipse OMR (https://github.com/eclipse/omr) and combines with the Extensions for OpenJDK for OpenJ9 repo.
Other
3.28k
stars
721
forks
source link
J9 crashed under JDK8 and JDK11 on the same test case. #15196
We found a test case with crash problems. To facilitate analysis, we simplified the test case and the simplified class file can ben found at attachment.
Microsoft Windows 10
11th Gen Intel(R) Core(TM) i7-11700F @ 2.50GHz 2.50 GHz
Memory 16.0 GB
Java -version output under Windows 10
openjdk version "1.8.0_322"
IBM Semeru Runtime Open Edition (build 1.8.0_322-b06)
Eclipse OpenJ9 VM (build openj9-0.30.0, JRE 1.8.0 Windows 10 amd64-64-Bit Compressed References 20220128_311 (JIT enabled, AOT enabled)
OpenJ9 - 9dccbe076
OMR - dac962a28
JCL - c1d9a7af7c based on jdk8u322-b06)
openjdk version "11.0.14.1" 2022-02-08
IBM Semeru Runtime Open Edition 11.0.14.1 (build 11.0.14.1+1)
Eclipse OpenJ9 VM 11.0.14.1 (build openj9-0.30.1, JRE 11 Windows 10 amd64-64-Bit Compressed References 20220210_305 (JIT enabled, AOT enabled)
OpenJ9 - 9dccbe076
OMR - 56c3376ba
JCL - 5c423dacd0 based on jdk-11.0.14.1+1)
Problem summary
We found that in a normal test case, if we executed the test case using J9-JDK8 or J9-JDK11 it would report crash, but if we executed it using Hotspot-JDK8 or -JDK11 it would print 'finish'. Below is the information we executed using J9-JDK11, and our test case can be found in the attachment.
0SECTION TITLE subcomponent dump routine
NULL ===============================
1TICHARSET 936
1TISIGINFO Dump Event "gpf" (00002000) received
1TIDATETIMEUTC Date: 2022/06/02 at 12:05:31:036 (UTC)
1TIDATETIME Date: 2022/06/02 at 20:05:31:036
1TITIMEZONE Timezone: (unavailable)
1TINANOTIME System nanotime: 15667875339600
1TIFILENAME Javacore filename: D:\projects\Bugs\target\classes\test\javacore.20220602.200527.2448.0002.txt
1TIREQFLAGS Request Flags: 0x41 (exclusive+preempt)
1TIPREPSTATE Prep State: 0x80 (trace_disabled)
1TIPREPINFO Exclusive VM access not taken: data may not be consistent across javacore sections
NULL ------------------------------------------------------------------------
0SECTION GPINFO subcomponent dump routine
NULL ================================
2XHOSLEVEL OS Level : Windows 10 10.0 build 19044
2XHCPUS Processors -
3XHCPUARCH Architecture : amd64
3XHNUMCPUS How Many : 16
3XHNUMASUP NUMA is either not supported or has been disabled by user
NULL
1XHEXCPCODE Windows_ExceptionCode: C0000005
1XHEXCPCODE J9Generic_Signal: 00000004
1XHEXCPCODE ExceptionAddress: 0000000000000000
1XHEXCPCODE ContextFlags: 0010005F
1XHEXCPCODE Handler1: 00007FF88BA4E750
1XHEXCPCODE Handler2: 00007FF8B4C7AA30
1XHEXCPCODE DEPAddress: 0000000000000000
NULL
1XHEXCPMODULE Module: D:\projects\cfsynthesis-v2.0\01JVMS\Windows\openjdk11\jdk-11.0.14.1+1_openj9\bin\java.exe
1XHEXCPMODULE Module_base_address: 0000000000000000
1XHEXCPMODULE Offset_in_DLL: 0000000000000000
NULL
Affected versions
We found a test case with crash problems. To facilitate analysis, we simplified the test case and the simplified class file can ben found at attachment.
Java -version output under Windows 10
Problem summary
We found that in a normal test case, if we executed the test case using J9-JDK8 or J9-JDK11 it would report crash, but if we executed it using Hotspot-JDK8 or -JDK11 it would print 'finish'. Below is the information we executed using J9-JDK11, and our test case can be found in the attachment.
Attachment
test.zip