Java process running on 64-bit JRE 6 Update 18 failed with the following
error message, after requesting 17179869200 bytes (= 16GB+16B) of memory.
# A fatal error has been detected by the Java Runtime Environment:
#
# java.lang.OutOfMemoryError: requested 17179869200 bytes for Chunk::new. Out of swap space?
#
# Internal Error (allocation.cpp:215), pid=4980, tid=1356
# Error: Chunk::new
#
# JRE version: 6.0_18-b07
# Java VM: Java HotSpot(TM) 64-Bit Server VM (16.0-b13 mixed mode windows-amd64 )
Comment added by ###@###.### :
The state of this bug is currently listed as "2-Incomplete, Need More Info". So here is information about how I am seeing this bug in production.
Following an upgrade from Java 1.5.0_06 to Java 1.6.0_20 (using the Server JVM in both instances), our production servers repeatedly crashed with this error.
Points of note:
* We're running Tomcat 5.5 on Windows 2000
* The compiler seems to be attempting to allocate 67M for the org.apache.velocity.runtime.directive.Foreach.render method
* There is plenty of free physical memory and address space (even though we're running 32-bit Windows)
* The heap size is nowhere near its configured maximum
Full details:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# java.lang.OutOfMemoryError: requested 67108872 bytes for Chunk::new. Out of swap space?
#
# Internal Error (allocation.cpp:215), pid=4992, tid=3312
# Error: Chunk::new
#
# JRE version: 6.0_20-b02
# Java VM: Java HotSpot(TM) Server VM (16.3-b01 mixed mode windows-x86 )
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
--------------- T H R E A D ---------------
Current thread (0x5edb2c00): JavaThread "CompilerThread0" daemon [_thread_in_native, id=3312, stack(0x5f0a0000,0x5f0e0000)]
Stack: [0x5f0a0000,0x5f0e0000], sp=0x5f0de8fc, free space=fa5f0de90ck
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [jvm.dll+0x323f60]
V [jvm.dll+0xff3dc]
V [jvm.dll+0x3e35c]
V [jvm.dll+0x3e5f3]
V [jvm.dll+0x297649]
V [jvm.dll+0x297c76]
V [jvm.dll+0x299675]
V [jvm.dll+0x298e8f]
V [jvm.dll+0xde65d]
V [jvm.dll+0xdf158]
V [jvm.dll+0xa46b1]
V [jvm.dll+0xe1359]
V [jvm.dll+0xe1eef]
V [jvm.dll+0x303d24]
V [jvm.dll+0x27e2ac]
C [MSVCR71.dll+0x9565]
C [KERNEL32.dll+0xb3bc]
Current CompileTask:
C2:3889 ! org.apache.velocity.runtime.directive.Foreach.render(Lorg/apache/velocity/context/InternalContextAdapter;Ljava/io/Writer;Lorg/apache/velocity/runtime/parser/node/Node;)Z (529 bytes)
It would be useful to get some sort of response to this bug report - either an indication of what work is in progress to fix it, or an indication of what further information is required.
error message, after requesting 17179869200 bytes (= 16GB+16B) of memory.
# A fatal error has been detected by the Java Runtime Environment:
#
# java.lang.OutOfMemoryError: requested 17179869200 bytes for Chunk::new. Out of swap space?
#
# Internal Error (allocation.cpp:215), pid=4980, tid=1356
# Error: Chunk::new
#
# JRE version: 6.0_18-b07
# Java VM: Java HotSpot(TM) 64-Bit Server VM (16.0-b13 mixed mode windows-amd64 )
Comment added by ###@###.### :
The state of this bug is currently listed as "2-Incomplete, Need More Info". So here is information about how I am seeing this bug in production.
Following an upgrade from Java 1.5.0_06 to Java 1.6.0_20 (using the Server JVM in both instances), our production servers repeatedly crashed with this error.
Points of note:
* We're running Tomcat 5.5 on Windows 2000
* The compiler seems to be attempting to allocate 67M for the org.apache.velocity.runtime.directive.Foreach.render method
* There is plenty of free physical memory and address space (even though we're running 32-bit Windows)
* The heap size is nowhere near its configured maximum
Full details:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# java.lang.OutOfMemoryError: requested 67108872 bytes for Chunk::new. Out of swap space?
#
# Internal Error (allocation.cpp:215), pid=4992, tid=3312
# Error: Chunk::new
#
# JRE version: 6.0_20-b02
# Java VM: Java HotSpot(TM) Server VM (16.3-b01 mixed mode windows-x86 )
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
--------------- T H R E A D ---------------
Current thread (0x5edb2c00): JavaThread "CompilerThread0" daemon [_thread_in_native, id=3312, stack(0x5f0a0000,0x5f0e0000)]
Stack: [0x5f0a0000,0x5f0e0000], sp=0x5f0de8fc, free space=fa5f0de90ck
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [jvm.dll+0x323f60]
V [jvm.dll+0xff3dc]
V [jvm.dll+0x3e35c]
V [jvm.dll+0x3e5f3]
V [jvm.dll+0x297649]
V [jvm.dll+0x297c76]
V [jvm.dll+0x299675]
V [jvm.dll+0x298e8f]
V [jvm.dll+0xde65d]
V [jvm.dll+0xdf158]
V [jvm.dll+0xa46b1]
V [jvm.dll+0xe1359]
V [jvm.dll+0xe1eef]
V [jvm.dll+0x303d24]
V [jvm.dll+0x27e2ac]
C [MSVCR71.dll+0x9565]
C [KERNEL32.dll+0xb3bc]
Current CompileTask:
C2:3889 ! org.apache.velocity.runtime.directive.Foreach.render(Lorg/apache/velocity/context/InternalContextAdapter;Ljava/io/Writer;Lorg/apache/velocity/runtime/parser/node/Node;)Z (529 bytes)
It would be useful to get some sort of response to this bug report - either an indication of what work is in progress to fix it, or an indication of what further information is required.
- duplicates
-
JDK-6916062 assert(_inserts <= _insert_limit,"hash table overflow") in NodeHash::hash_insert with debug build
- Resolved