-
Bug
-
Resolution: Fixed
-
P2
-
6
This time, Dan found some JDI regression tests failing on minh:
Greetings,
Looks there are some new failures in last night's main/baseline
testing. 9 JDI_REGRESSION tests failed on Solaris X86 Client VM and 35
JDI_REGRESSION tests failed on Solaris X86 Server VM:
Internal Error (494E5445525052455445520E435050014E)
Java VM: Java HotSpot(TM) Server VM (20050825070300.mingyao.rt_merge mixed mode)
This ErrorID is:
interpreter.cpp, 334
which is the following code in src/share/vm/interpreter/interpreter.cpp:
_clet = (InterpreterCodelet*)AbstractInterpreter::code()->request(codelet_si
ze);
guarantee(_clet != NULL, "not enough space for interpreter generation");
This occurred on test machine minh which seems to be really
good at finding these code size issues.
Greetings,
Looks there are some new failures in last night's main/baseline
testing. 9 JDI_REGRESSION tests failed on Solaris X86 Client VM and 35
JDI_REGRESSION tests failed on Solaris X86 Server VM:
Internal Error (494E5445525052455445520E435050014E)
Java VM: Java HotSpot(TM) Server VM (20050825070300.mingyao.rt_merge mixed mode)
This ErrorID is:
interpreter.cpp, 334
which is the following code in src/share/vm/interpreter/interpreter.cpp:
_clet = (InterpreterCodelet*)AbstractInterpreter::code()->request(codelet_si
ze);
guarantee(_clet != NULL, "not enough space for interpreter generation");
This occurred on test machine minh which seems to be really
good at finding these code size issues.
- relates to
-
JDK-6282076 jdi_regression/nsk.jvmti failures ONLY on machine minh.sfbay
- Closed
-
JDK-6434225 64bit JVM abort with internal error during initialization using debug options
- Closed
-
JDK-4902759 hotspot should not hard code CodeBuffer sizes
- Closed