Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2039653 | 1.4.0 | John Coomes | P4 | Closed | Fixed | beta |
compiler. The interpreter and client compiler changes were fixed under bug
4298656.
Problem is that the stack yellow zone is disabled on the first occurrence
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-2039653 [server] stack yellow zone not re-enabled after a StackOverflowError
-
- Closed
-
- duplicates
-
JDK-4400369 cgt (js) test crashes with assertion at sharedRuntime.cpp, 168
-
- Closed
-
-
JDK-6225936 J2SE 1.3.1_11 on WebLogic Server 6.1 server instances keep crashing every few hour on Solaris 8
-
- Closed
-
-
JDK-4302287 the second stack overflow crashes HotSpot Server VM on Solaris
-
- Closed
-
-
JDK-4302289 the second stack overflow causes HotSpot Server VM to exit on win32
-
- Closed
-
-
JDK-4396960 HotSpot Virtual Machine Error, EXCEPTION_STACK_OVERFLOW
-
- Closed
-
- relates to
-
JDK-4427144 [server] StackOverflow.java causes SEGV on solaris sparc
-
- Closed
-
-
JDK-4736391 irrecoverable stack overflow using 1.3.1)4
-
- Closed
-
-
JDK-4298656 stack yellow zone not re-enabled after a StackOverflowError
-
- Closed
-