-
Enhancement
-
Resolution: Fixed
-
P3
-
1.4.2, 1.4.2_18
-
b07
-
generic, x86
-
windows, windows_2003, windows_xp
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2173253 | 5.0-pool | Kevin Walls | P5 | Closed | Won't Fix | |
| JDK-2174441 | 1.4.2_21 | Kevin Walls | P3 | Closed | Fixed | b01 |
For most of 1.4.2's life, the command-line option CompilerThreadStackSize was not recognised on the Windows platform.
In 1.4.2_18 CompilerThreadStackSize is recognised on Windows.
Some advice exists to use -Xss as an alternative way of getting larger stack for the hotspot CompilerThread.
This no longer works, as was the intention.
The enhancement request here is to recognise the -Xss (ThreadStackSize) setting for the CompilerThread, IF CompilerThreadStackSize is not being specified.
If implemented, this will mean there is only a small window of update release history in which -Xss does not set the CompilerThread. stack.
In 1.4.2_18 CompilerThreadStackSize is recognised on Windows.
Some advice exists to use -Xss as an alternative way of getting larger stack for the hotspot CompilerThread.
This no longer works, as was the intention.
The enhancement request here is to recognise the -Xss (ThreadStackSize) setting for the CompilerThread, IF CompilerThreadStackSize is not being specified.
If implemented, this will mean there is only a small window of update release history in which -Xss does not set the CompilerThread. stack.
- backported by
-
JDK-2174441 Adjust CompilerThreadStackSize being recognised for backwards compatibility.
-
- Closed
-
-
-
- Closed
-
- duplicates
-
JDK-6784583 Compiler thread size leads to issues
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Resolved
-