The stack for the main thread is created by the o/s when the process is
created; the vm cannot later increase the size of this stack. The stack
sizes for other java threads created by the vm are (mostly) controlled
by the vm, and use the -Xss<N> value or a default. (The 'mostly' is
because of operating system eccentricities.)
The different stack sizes for the main thread vs. other threads means
that some (typically recursive) routines may be able to run in one
thread, but not in another. It also means that the -Xss<N> argument
to set the thread stack size does not apply to all threads, at least
on some platforms. This asymmetry should be eliminated.
created; the vm cannot later increase the size of this stack. The stack
sizes for other java threads created by the vm are (mostly) controlled
by the vm, and use the -Xss<N> value or a default. (The 'mostly' is
because of operating system eccentricities.)
The different stack sizes for the main thread vs. other threads means
that some (typically recursive) routines may be able to run in one
thread, but not in another. It also means that the -Xss<N> argument
to set the thread stack size does not apply to all threads, at least
on some platforms. This asymmetry should be eliminated.
- duplicates
-
JDK-4854196 -Xss does not work on Win32 causing Java application to crash(Stack Overflow)
- Closed
-
JDK-4731363 JCK tests failed with exit code 128
- Closed
-
JDK-6316197 Java launcher should create JVM from non-primordial thread
- Resolved
- relates to
-
JDK-4678676 Reg-test ReflectStackOverflow.java Failing
- Closed
-
JDK-4675952 java.util.regex routines should use less stack space
- Open
-
JDK-6291845 Test iload_w00310m1t8p failed with runtime exception java.lang.StackOverflowError
- Closed
(1 relates to)