###@###.### 2002-06-26

During the last month messages displaying "out of memory" have become more common. I've seen this a few times while running the JCK harness with jdk1.3.1_04. (while testing the 1.4.0_01 jdk) I initially thought this was a memory resource problem with the machine but I think it may be a more serious issue with the jdk.

I've seen it on both Linux and XP Pro.
I've had feedback from other engineers saying that they have also experienced a similar memory problem while using the jdk1.4.0_01 jdk to run tests.

The errors normally start appearing after a few thousand tests have been executed.

Included are examples from linux and winxp. :


Windows XP :

C:\>cd jck13^M
^M
C:\jck13>set CLASSPATH=z:/jck/JCK-runtime-13a/javatest.jar;z:/jck/JCK-runtime-13
^M
a/classes^M
^M
C:\jck13>ksh LiM.ksh^M
^M
C:\jck13>Initial Naming Context:^M
IOR:000000000000002849444c3a6f6d672e6f72672f436f734e616d696e672f4e616d696e67436f
^M
6e746578743a312e300000000001000000000000005c000101000000000f3132392e3135362e3233
^M
332e37330000040e000000000019afabcaff00000002bd04637d0000000800000000000000000100
^M
00000000000100000001000000140000000000010020000000000001010000000000^M
TransientNameServer: setting port for initial object references to: 9876^M
Ready.^M
java.lang.OutOfMemoryError^M
        <<no stack trace available>>^M
java.lang.OutOfMemoryError^M
        <<no stack trace available>>^M
java.lang.OutOfMemoryError^M
        <<no stack trace available>>^M
java.lang.OutOfMemoryError^M
        <<no stack trace available>>^M
java.lang.OutOfMemoryError^M
        <<no stack trace available>>^M
java.lang.OutOfMemoryError^M
        <<no stack trace available>>^M
java.lang.OutOfMemoryError^M
        <<no stack trace available>>^M
Exception occurred during event dispatching:^M
java.lang.OutOfMemoryError^M
        <<no stack trace available>>^M
java.lang.OutOfMemoryError^M
        <<no stack trace available>>^M
java.lang.OutOfMemoryError^M
        <<no stack trace available>>^M
Exception occurred during event dispatching:^M
An unexpected exception has been detected in native code outside the VM.^M
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6d0d58d3^M
Function name=JNI_OnLoad^M
Library=C:\jdk1.3.1_04\jre\bin\awt.dll^M
^M
Current Java thread:^M
        at sun.awt.windows.WToolkit.eventLoop(Native Method)^M
        at sun.awt.windows.WToolkit.run(WToolkit.java:183)^M
        at java.lang.Thread.run(Thread.java:479)^M
^M
Dynamic libraries:^M
0x00400000 - 0x00405000 C:\jdk1.3.1_04\bin\java.EXE^M
0x77F50000 - 0x77FF9000 C:\WINDOWS\System32\ntdll.dll^M
0x77E60000 - 0x77F45000 C:\WINDOWS\system32\kernel32.dll^M
0x77DD0000 - 0x77E5B000 C:\WINDOWS\system32\ADVAPI32.dll^M
0x77CC0000 - 0x77D35000 C:\WINDOWS\system32\RPCRT4.dll^M
0x77C10000 - 0x77C63000 C:\WINDOWS\system32\MSVCRT.dll^M
0x6D420000 - 0x6D4F7000 C:\jdk1.3.1_04\jre\bin\hotspot\jvm.dll^M
0x77D40000 - 0x77DCD000 C:\WINDOWS\system32\USER32.dll^M
0x77C70000 - 0x77CB0000 C:\WINDOWS\system32\GDI32.dll^M
0x76B40000 - 0x76B6C000 C:\WINDOWS\System32\WINMM.dll^M
0x6D220000 - 0x6D227000 C:\jdk1.3.1_04\jre\bin\hpi.dll^M
0x6D3B0000 - 0x6D3BD000 C:\jdk1.3.1_04\jre\bin\verify.dll^M
0x6D250000 - 0x6D266000 C:\jdk1.3.1_04\jre\bin\java.dll^M
0x6D3C0000 - 0x6D3CD000 C:\jdk1.3.1_04\jre\bin\zip.dll^M
0x6D020000 - 0x6D12A000 C:\jdk1.3.1_04\jre\bin\awt.dll^M
0x73000000 - 0x73023000 C:\WINDOWS\System32\WINSPOOL.DRV^M
0x76390000 - 0x763AA000 C:\WINDOWS\System32\IMM32.dll^M
0x771B0000 - 0x772CA000 C:\WINDOWS\system32\ole32.dll^M
0x6D1E0000 - 0x6D21B000 C:\jdk1.3.1_04\jre\bin\fontmanager.dll^M
0x6D340000 - 0x6D348000 C:\jdk1.3.1_04\jre\bin\net.dll^M
0x71AD0000 - 0x71AD8000 C:\WINDOWS\System32\WSOCK32.dll^M
0x71AB0000 - 0x71AC5000 C:\WINDOWS\System32\WS2_32.dll^M
0x71AA0000 - 0x71AA8000 C:\WINDOWS\System32\WS2HELP.dll^M
0x71A50000 - 0x71A8B000 C:\WINDOWS\system32\mswsock.dll^M
0x71A90000 - 0x71A98000 C:\WINDOWS\System32\wshtcpip.dll^M
0x76F20000 - 0x76F45000 C:\WINDOWS\System32\DNSAPI.dll^M
0x76FB0000 - 0x76FB7000 C:\WINDOWS\System32\winrnr.dll^M
0x76F60000 - 0x76F8C000 C:\WINDOWS\system32\WLDAP32.dll^M
0x73760000 - 0x737A5000 C:\WINDOWS\System32\ddraw.dll^M
0x73BC0000 - 0x73BC6000 C:\WINDOWS\System32\DCIMAN32.dll^M
0x11C00000 - 0x11C3D000 C:\Program Files\Network Associates\VirusScan\Wb
^M
hook32.dll^M
0x77C00000 - 0x77C07000 C:\WINDOWS\system32\VERSION.dll^M
0x10000000 - 0x10009000 C:\Program Files\Network Associates\VirusScan\Re
^M
s09\WbhkRes.dll^M
0x76FC0000 - 0x76FC5000 C:\WINDOWS\System32\rasadhlp.dll^M
0x76C90000 - 0x76CB2000 C:\WINDOWS\system32\imagehlp.dll^M
0x6D510000 - 0x6D58C000 C:\WINDOWS\system32\DBGHELP.dll^M
0x76BF0000 - 0x76BFB000 C:\WINDOWS\System32\PSAPI.DLL^M
^M
Local Time = Tue Apr 23 10:51:38 2002^M
Elapsed Time = 1206^M
#^M
# The exception above was detected in native code outside the VM^M
#^M
# Java VM: Java HotSpot(TM) Client VM (1.3.1_04-ea-b01 mixed mode)^M
#^M
# An error report file has been saved as hs_err_pid632.log.^M
^^^^^^^^^^^^^^^^^^ contains same info as above....
# Please refer to the file for further information.^M
#^M
====================================================================

Output from Linux 7.2 :

Exception in thread "AWT-Motif" Exception in thread "AWT-Motif" java.lang.OutOfM
emoryError
        <<no stack trace available>>
Exception in thread "AWT-Motif" java.lang.OutOfMemoryError
        <<no stack trace available>>
Exception in thread "AWT-Motif" java.lang.OutOfMemoryError
        <<no stack trace available>>
Exception in thread "AWT-Motif" java.lang.OutOfMemoryError
        <<no stack trace available>>
Exception in thread "AWT-Motif" java.lang.OutOfMemoryError
Exception in thread "AWT-Motif" java.lang.OutOfMemoryError
Exception in thread "AWT-Motif" java.lang.OutOfMemoryError
Exception in thread "AWT-Motif" java.lang.OutOfMemoryError
Exception in thread "AWT-Motif" java.lang.OutOfMemoryError
Exception in thread "AWT-Motif" java.lang.OutOfMemoryError