Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2030712 | 1.4.0 | John Coomes | P4 | Closed | Fixed | beta |
of a stack overflow for a thread, but never re-enabled after the
StackOverflowError is thrown. The next stack overflow thus enters the
red zone, which the vm treats as fatal. The attached simple java program
so2.java demonstrates this.
- backported by
-
JDK-2030712 stack yellow zone not re-enabled after a StackOverflowError
-
- Closed
-
- duplicates
-
JDK-4424017 HotSpot Virtual Machine Error : 11 with os.cpp file in Int mode
-
- Closed
-
-
JDK-4736567 JVM SEGV's after issuing "An irrecoverable stack overflow has occurred."
-
- Closed
-
-
JDK-4352424 Linux: StackOverflow problem
-
- Closed
-
-
JDK-4281578 Second stack overflow crashes HotSpot VM
-
- Closed
-
-
JDK-4282531 c1-101899 running 2 jck StackOverFlow tests consecutively exit the VM in comp
-
- Closed
-
-
JDK-4366625 multiple stack overflow causes HS crash
-
- Closed
-
-
JDK-4377163 HotSpot reports a stack overflow, when it should really be a StackOverflowError
-
- Closed
-
-
JDK-4381856 HotSpot reports internal error instead of StackOverflowError (win98)
-
- Closed
-
-
JDK-4525530 REGRESSION: Stack overflow and Error ID: 53484152454432554E54494D450E43505000DB
-
- Closed
-
-
JDK-4925317 overflow VM tests fails on SuSe8.2 for 1.3.1_x
-
- Closed
-
- relates to
-
JDK-4377621 exception stack overflow Error ID: 4F533F57494E13120E43505002D4
-
- Closed
-
-
JDK-4402735 [server] stack yellow zone not re-enabled after a StackOverflowError
-
- Closed
-
-
JDK-4296554 JCK vm test exceptions03102 fails with HotSpot, Solaris in singleJVM mode
-
- Closed
-
-
JDK-4736391 irrecoverable stack overflow using 1.3.1)4
-
- Closed
-
-
JDK-4285716 native stack overflow causes crash on Solaris
-
- Closed
-