United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 6778571 Adjust CompilerThreadStackSize being recognised for backwards compatibility.
6778571 : Adjust CompilerThreadStackSize being recognised for backwards compatibility.

Details
Type:
Enhancement
Submit Date:
2008-12-01
Status:
Closed
Updated Date:
2012-10-13
Project Name:
JDK
Resolved Date:
2009-01-12
Component:
hotspot
OS:
windows_2003,windows_xp,windows
Sub-Component:
runtime
CPU:
x86,generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
1.4.2,1.4.2_18
Fixed Versions:
1.4.2_19-rev

Related Reports
Backport:
JDK-2174441 - Adjust CompilerThreadStackSize being recognised for backwards compatibility.
Backport:
JDK-2173253 - Adjust CompilerThreadStackSize being recognised for backwards compatibility.
Duplicate:
JDK-6784583 - Compiler thread size leads to issues
Duplicate:
JDK-6736207 - JVM crash with STACK_OVERFLOW exception
Relates:
JDK-6579892 - 1.4.2_12 server VM fails with EXCEPTION_STACK_OVERFLOW on Windows in PhaseCFG::set_pinned

Sub Tasks

Description
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.

Comments
EVALUATION

Change logic for recognising stack settings when creating CompilerThread, to recognise -Xss value if CompilerThreadStackSize is not set.
2008-12-18


Hardware and Software, Engineered to Work Together