Details
-
Bug
-
Resolution: Fixed
-
P3
-
2.0
-
rc1
-
x86
-
windows_nt
Description
HotSpot crashes when executing HS 2.0-rc1G / JDK 1.2.2 under WinNT in -Xcomp mode
against some JCK-stress tests belonging to the Novosibirsk testbase 'testbase_nsk'.
This testbase is located in the directory:
/net/sqesvr/vsn/testbase/testbase_nsk
and the tests are located in the sub-directory:
${TESTBASE_NSK}/src
The tests caused HS crash are:
nsk/stress/jck12a/jck12a003
nsk/stress/jck122/jck122006
Here is the diagnostics printed when HS crashed:
Exit status of Execution is :-1073741819
Before the crash, Windows have shown the following error message:
java.exe -- Application Error
The instruction at "0x080016ce" referenced memory at "0x00000004".
The memory could not be "read".
and MS VC++ 6.0 debugger complained:
Unhandled exception in java.exe (JVM.DLL): 0xC0000005: Access Violation.
The JCK-stress tests are based on JCK 1.2a and JCK 1.2.2, and try to
execute large bunches of JCK tests simultaneously as concurrent threads.
In particular, the test 'jck12a003' executes 842 of JCK 1.2a tests, and
the test 'jck122006' executes 488 of JCK 1.2.2 tests.
To execute these tests you need to have the following stuff in the CLASSPATH:
/usr/local/java/sqe-tools2.0/javatest.jar
/usr/local/java/jck1.2/JCK-runtime-lang-12a/classes (needed only for tests: jck12a001-004)
/usr/local/java/jck1.2.2/JCK-runtime-lang-122/classes (needed only for tests: jck122001-006)
Also, it is necessary to compile the stress-wrapper:
${TESTBASE_NSK}/src/nsk/stress/share/StressTest.java
and append its binary to the CLASSPATH.
Note, that some JCK tests need '-Xfuture' or '-verify' option to run correctly;
so you need to set '-verify' option to execute the JCK-stress tests, e.g:
java -Xcomp -verify jck12a003 2>log
###@###.###, 5 nov 1999:
I still observe exactly the same problem with the HS 2.0-rc1B
nsk/stress/jck12a/jck12a003
against some JCK-stress tests belonging to the Novosibirsk testbase 'testbase_nsk'.
This testbase is located in the directory:
/net/sqesvr/vsn/testbase/testbase_nsk
and the tests are located in the sub-directory:
${TESTBASE_NSK}/src
The tests caused HS crash are:
nsk/stress/jck12a/jck12a003
nsk/stress/jck122/jck122006
Here is the diagnostics printed when HS crashed:
Exit status of Execution is :-1073741819
Before the crash, Windows have shown the following error message:
java.exe -- Application Error
The instruction at "0x080016ce" referenced memory at "0x00000004".
The memory could not be "read".
and MS VC++ 6.0 debugger complained:
Unhandled exception in java.exe (JVM.DLL): 0xC0000005: Access Violation.
The JCK-stress tests are based on JCK 1.2a and JCK 1.2.2, and try to
execute large bunches of JCK tests simultaneously as concurrent threads.
In particular, the test 'jck12a003' executes 842 of JCK 1.2a tests, and
the test 'jck122006' executes 488 of JCK 1.2.2 tests.
To execute these tests you need to have the following stuff in the CLASSPATH:
/usr/local/java/sqe-tools2.0/javatest.jar
/usr/local/java/jck1.2/JCK-runtime-lang-12a/classes (needed only for tests: jck12a001-004)
/usr/local/java/jck1.2.2/JCK-runtime-lang-122/classes (needed only for tests: jck122001-006)
Also, it is necessary to compile the stress-wrapper:
${TESTBASE_NSK}/src/nsk/stress/share/StressTest.java
and append its binary to the CLASSPATH.
Note, that some JCK tests need '-Xfuture' or '-verify' option to run correctly;
so you need to set '-verify' option to execute the JCK-stress tests, e.g:
java -Xcomp -verify jck12a003 2>log
###@###.###, 5 nov 1999:
I still observe exactly the same problem with the HS 2.0-rc1B
nsk/stress/jck12a/jck12a003
Attachments
Issue Links
- relates to
-
JDK-4239828 1.3c1: VM crashes when heap is exhausted
-
- Closed
-
-
JDK-4286051 intermittent JCK test failures under stressed-out execution
-
- Closed
-
-
JDK-4288411 intermittent memory access violation at the test 'jck12a011'
-
- Closed
-