-
Bug
-
Resolution: Fixed
-
P3
-
osol_2009.06, solaris_11, hs19, 5.0u13, 6, 6u2, 6u5, 6u10, 6u11, 6u23, 7
-
b06
-
generic, x86, sparc
-
generic, linux, linux_redhat_4.0, open_solaris, solaris_nevada, solaris_10, windows, windows_xp
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2205079 | 7 | Coleen Phillimore | P3 | Closed | Fixed | b125 |
JDK-2205904 | 6u25 | Coleen Phillimore | P3 | Closed | Fixed | b01 |
JDK-2184030 | 5.0-pool | Dmitriy Samersoff | P3 | Closed | Won't Fix |
Platform[s] : Fails On: winXP Prof.
Failing Test [s] : CTE_REGTEST/Generic/4765019/ThreadTest.java
Test source location:
=====================
/net/jdk/export/jpse04/Regression/1.6.0/test/CTE_REGTEST/Generic/4765019/ThreadTest.java
jtr file location:
==================
/net/cady/export6/results/mustang/b44/reg/regression-cte-reg-XPpro-2005-07-25-10-50-09-0981/workDir/CTE_REGTEST/Generic/4765019/ThreadTest.jtr
How to reproduce:
====================
- Set JAVA_HOME to Mustang b44 windows-i586
- cd /net/jdk/export/jpse04/Regression/1.6.0/test/CTE_REGTEST/Generic/4765019
- /net/koori.sfbay/onestop/jct-tools/2.1.6/archive/fcs/binaries/win32/bin/jtreg -r:/tmp -w:/tmp ThreadTest.java
Test output:
=============
----------System.out:(14/486)----------
Exception in thread "main" java.lang.OutOfMemoryError: unable to create new native thread
7104
7105
7106
7107
7108
7109
Exception in thread "main" java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:587)
at ThreadTest.main(ThreadTest.java:17)
Unrecognized VM option '+UseDefaultStackSize'
Unrecognized VM option '+UseDefaultStackSize'
Could not create the Java virtual machine.
----------System.err:(46/1418)*----------
java full version "1.6.0-ea-b44"
+ grep Unrecognized VM option test.out
+ [ 1 != 0 ]
+ + wc -l test.out
+ awk {print $1}
L_NO=7114
+ grep OutOfMemoryError test.out
+ [ 0 = 0 ]
+ + grep -n OutOfMemoryError test.out
+ cut -f1 -d :
L_NO=7111
+ + expr 7111 - 1
L_NO=7110
+ + head -7110 test.out
+ tail -1
VAL=7109
+ tail test.out
+ VAL1=7109
+ [ 7109 = 0 ]
+ Execute_Command -Xss256K -XX:+UseDefaultStackSize 0 22616
+ cd Y:/dtf/unified/knight-ws/exec/regression-cte-reg-XPpro-2005-07-25-10-50-09-0981/results/workDir/scratch
+ VAL=0
+ rm -f test.out
+ C:/jdk/b44/windows-i586/jdk1.6.0\\bin\\java -Xss256K -XX:+UseDefaultStackSize ThreadTest
+ sleep 10
+ [ 0 = 0 ]
+ + ps
+ grep ThreadTest
+ grep -v grep
+ awk {print $1}
C_PID=
+ sleep 120
+ kill -s 9
kill: Execute_Command 3: Y:\\dtf\\unified\\knight-ws\\suites\\regression\\cte-test\\CTE_REGTEST\\Generic\\4765019\\Test4765019.sh 128: Usage: kill -l [status]
kill [-s SIGNAL] job ...
+ chmod 777 ThreadTest.class test.out
+ set -x
+ grep Unrecognized VM option test.out
+ [ 0 != 0 ]
+ tail test.out
+ VAL3=0
+ + echo 7109
+ awk {AA = $1; BB = AA * 0.9; print BB}
VAL4=6398.1
+ [ 0 -ge 7109 -o 0 -ge 6398.1 ]
[: Y:\\dtf\\unified\\knight-ws\\suites\\regression\\cte-test\\CTE_REGTEST\\Generic\\4765019\\Test4765019.sh 141: unknown operator in arithmetic expression "6398.1" near 8.
result: Failed. Execution failed: exit code 1
The hs_err* file is incomplete because it gets an error while printing out all of the threads, but if I comment out that part of vmError.cpp, I can get a stack trace:
Stack: [0xf5da0000,0xf5de0000), sp=0xf5ddeb0c, free space=250k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x8f9c47] void VMError::report_and_die()+0x597
V [libjvm.so+0x38cbee] void report_vm_out_of_memory(const char*,int,unsigned,const char*)+0xae
V [libjvm.so+0x1ee067] void*Chunk::operator new(unsigned,unsigned)+0xf7
V [libjvm.so+0x1ee90f] void*Arena::grow(unsigned)+0x4f
V [libjvm.so+0x1ef9ef] void*Arena::Amalloc(unsigned)+0xbf
V [libjvm.so+0x330aef] Node_Stack::Node_Stack(int)+0x7f
V [libjvm.so+0x6bdbd4] MStack::MStack(int)+0x34
V [libjvm.so+0x6baa06] void Matcher::find_shared(Node*)+0x56
V [libjvm.so+0x6b61a5] void Matcher::match()+0x705
V [libjvm.so+0x32d255] void Compile::Code_Gen()+0xc5
V [libjvm.so+0x32990c] Compile::Compile(ciEnv*,C2Compiler*,ciMethod*,int,bool)+0xd1c
V [libjvm.so+0x24ffe7] void C2Compiler::compile_method(ciEnv*,ciMethod*,int)+0x77
V [libjvm.so+0x33860b] void CompileBroker::invoke_compiler_on_method(CompileTask*)+0x3d7
V [libjvm.so+0x337e2c] void CompileBroker::compiler_thread_loop()+0x3a4
V [libjvm.so+0x88e046] void compiler_thread_entry(JavaThread*,Thread*)+0x66
V [libjvm.so+0x8891cc] void JavaThread::thread_main_inner()+0x15c
V [libjvm.so+0x88905e] void JavaThread::run()+0x11e
V [libjvm.so+0x732c2e] java_start+0x19e
C [libc.so.1+0x9f6f8] _thr_setup+0x4e
C [libc.so.1+0x9f9e0] _lwp_start+0x0
The compiler is still running when the VM runs out of memory, and blows up trying to allocate memory for compilation.
To get this on x86 -server run: java -mx10m ThreadTest
- backported by
-
JDK-2184030 Hotspot VM dies ungraceful death when C heap is exhausted in various places.
- Closed
-
JDK-2205079 Hotspot VM dies ungraceful death when C heap is exhausted in various places.
- Closed
-
JDK-2205904 Hotspot VM dies ungraceful death when C heap is exhausted in various places.
- Closed
- duplicates
-
JDK-6644629 JVM dies with little/misleading problem information during excessive creation of ORB threads
- Closed
-
JDK-6892275 java is core dumping with osol_1002-124 out of swap space
- Closed
-
JDK-6702782 java is core dumping on sparc when out of C heap.
- Closed
-
JDK-6748784 NetBeans Debugger session causes VM crash - out of C heap
- Closed
-
JDK-6981006 VM doesn't exit gracefully when C heap is exhausted
- Closed
-
JDK-7006676 JVM behaves inconsistently during initialization on sun4u vs sun4v platforms
- Closed
-
JDK-6601634 When too many threads are created, JVM crashes with "ChunkPool::allocate. Out of swap space?"
- Closed
-
JDK-6627258 SIGBUS in C2 compiled method - not enough swap space for thread stack (add message)
- Closed
- relates to
-
JDK-6896673 java is core dumping with osol_1002-124 assert("offset table expansion") out of C heap
- Closed
-
JDK-7013634 jvmti resexhausted001 can timeout or fail due to excessive thread creation
- Closed