Customer Problem description:
-----------------------------

After running through many iterations of our routines, something bad eventually happens:
1. out of memory error, java.exe exits
2. java.exe crashes, in native code
3. jvm exception, java.exe exits

We're running the hotspot client vm:
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C)
Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)



1. out of memory:

E:\test\java>java -classpath dialogserver.jar;parser.jar;servlet.jar;jaxp.jar;.
-Detc=. -Xms160M -Xmx160M EngineLoadTest2 files\demos\mutuallife\mlife.htm -a -t
8 -i-1
Input: files\demos\mutuallife\mlife.htm
Output: none
Caching: true
Browser: IE5
Iterations: -1
Threads: 8
Compression: false
Inline JS: true
TerseOutput: false
File Size: 263,447 bytes

Computed Adler = 6e87d7f3

Press Enter to Stop

          Pages Seconds Pages/Sec
         29,793 928 32java.lang.OutOfMemoryError
        <<no stack trace available>>

E:\test\java>

2. java.exe crash
[GC 28602K->27230K(32576K), 0.0192270 secs]
[GC 29328K->27573K(32576K), 0.0113367 secs]
[GC 29685K->28110K(32576K), 0.0157567 secs]
[GC 30217K->28658K(32576K), 0.0155967 secs]
[Full GC 30768K->12316K(32576K), 0.5985409 secs]
#
# An EXCEPTION_ACCESS_VIOLATION exception has been detected in native code
outside the VM.
# Program counter=0x103
#
        965,068 19,365 55
        

3. jvm exception

C:\test\java>java -classpath dialogserver.jar;parser.jar;servlet.jar;. -Detc=c:test\java -Xms128M -Xmx128M EngineLoadTest2 dialogserver/demos/mutuallife/mlife.
htm -i-1 -t3 -a
Input: dialogserver/demos/mutuallife/mlife.htm
Output: none
Caching: true
Browser: IE5
Iterations: -1
Threads: 3
Compression: false
Inline JS: false
TerseOutput: true
File Size: 111,368 bytes

Computed Adler = a3932c78

Press Enter to Stop

          Pages Seconds Pages/Sec
        125,587 7,307 12#
# HotSpot Virtual Machine Error, EXCEPTION_ACCESS_VIOLATION
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error ID: 4F533F57494E13120E43505002D4
#

abnormal program termination

C:\test\java>


Similar behaviour is seen with 1.3.0_01 as well:

C:\TEMP>runtest2

C:\TEMP>jrcs -d -t8 -i-1

C:\TEMP>call jr dialogserver\samples\colorshape\colorshape.htm -d -t8 -i-1


C:\TEMP>java -showversion -classpath dialogserver.jar;parser.jar;servlet.jar;. -
Detc=. -Xms32M -Xmx32M EngineLoadTest2 dialogserver\samples\colorshape\colorshap
e.htm -d -t8 -i-1
java version "1.3.0_01-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0_01-beta)
Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)

Input: dialogserver\samples\colorshape\colorshape.htm
Output: none
Caching: false
System.gc(): 0
Browser: IE5
Iterations: -1
Threads: 8
Compression: true
Inline JS: false
TerseOutput: true
File Size: 2,481 bytes

Press Enter to Stop

          Pages Seconds Pages/Sec
            629 27 25#
# HotSpot Virtual Machine Error, EXCEPTION_ACCESS_VIOLATION
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error ID: 4F533F57494E13120E43505002D4
#

abnormal program termination


Unfortunately, we can't
duplicate the problem with 100% consistency. However, we are often able
to get some type of problem to occur within a few hours of run time. Also,
I'm fairly certain that increasing the heap size will just delay the
problem We first detected the problem with a heap size of -Xms256M
-Xmx256M. It was a slightly different test, but it ran for 1-2 days and
processed between 4 and 16 million pages before crashing the jvm.

Attached is a self-extracting zip that should include all the files you
need. Extract it to an empty directory, and run the runtest.bat file you
find there. It should crash or run out of memory after running a while.

Info on the two machines we've seen the problems on are also attached.
They're reports from the Windows NT Diagnostics utility.

Name: yyT116575 Date: 01/09/2001


C:\>java -version
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C)
Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)


Test Platform: Dell Inspiron 7000 PentiumII 400, 256MB ram,
running JVM 1.3 with vmargs: -mx8m (purposely starting small)

Using OptimizeIt 4.01 Pro (build 413) Intuit Systems www.optimizeit.com
to track down memory leak. Running in conjunction with JSW 2.0.
Selected "reference graph" option. After lengthy (2 minute pause) with CPU at
100% usage, following error produced:

This can be repeated upon demand.

javawebserver: abnormal program termination
javawebserver: OptimizeIt generic Audit System. [Hotspot runtime detected]
javawebserver: #
javawebserver: # HotSpot Virtual Machine Error, EXCEPTION_ACCESS_VIOLATION
javawebserver: # Please report this error at
javawebserver: # http://java.sun.com/cgi-bin/bugreport.cgi
javawebserver: #
javawebserver: # Error ID: 4F533F57494E13120E43505002D4
javawebserver: #
javawebserver: High-resolution counter available
javawebserver: C:\JavaWebServer2.0\bin\..\bin\jserv.exe
javawebserver: C:\JAVAWE~1.0\bin\..\bin\jserv.exe
javawebserver: Program C:\JDK1.3\bin\java.exe exited with code 3
Java Web Server WARNING: Server javawebserver unexpectedly exited with code 3
(Review ID: 114819)
======================================================================

Name: yyT116575 Date: 01/17/2001


java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C)
Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)


HotSpot gives me random memory weirdness -- first, using OptimizeIt 4.0 and comparing it with the Windows NT task manager, I can see that, for example, the VM has allocated 200+ megs of RAM. However, OptimizeIt reports that the java heap is roughly 20-40 megabytes.

Sometimes, HotSpot crashes with an error such as the following (which is an actual error message that I have just received):

#
# HotSpot Virtual Machine Error, EXCEPTION_ACCESS_VIOLATION
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error ID: 4F533F57494E13120E43505002D4
#

abnormal program termination

This happens on Windows NT 4.0, service pack 6a, although we are getting the same type of weirdness on other types of Windows systems.
(Review ID: 115271)
======================================================================