JDK-6579892 : 1.4.2_12 server VM fails with EXCEPTION_STACK_OVERFLOW on Windows in PhaseCFG::set_pinned
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 1.4.2_12,1.4.2_13
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_2003
  • CPU: x86
  • Submitted: 2007-07-12
  • Updated: 2010-12-02
  • Resolved: 2008-05-01
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other Other Other Other Other
1.4.2_16-rev b08Fixed 1.4.2_17-revFixed 1.4.2_18Fixed 5.0u16-revFixed 5.0u17Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
For 1.4.2_12, and 1.4.2_13, server VM the following failure was reported:

1. error log
------------
Please find several hs_err_pid.log files attached:

% #
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  EXCEPTION_STACK_OVERFLOW (0xc00000fd) at pc=0x00000000080e2896, pid=6660, tid=1976
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.4.2_12-b03 mixed mode)
# Problematic frame:
# V  [jvm.dll+0xe2896]
#

---------------  T H R E A D  ---------------

Current thread (0x0000000001276b70):  JavaThread "CompilerThread1" daemon [_thread_in_native, id=1976]

[ ... ]

Stack: [0x00000000064c0000,0x0000000006500000),  sp=0x00000000064c1000,  free space=4k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V  [jvm.dll+0xe2896]


Current CompileTask:
opto:867  !   com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendMessage(Lcom/sap/engine/core/cluster/impl6/ms/MSMessageObjectImpl;Lcom/sap/engine/core/cl
uster/impl6/ms/MSRegistrable;[BIIZ)Lcom/sap/engine/frame/cluster/message/MessageAnswer; (1477 bytes)
[ ... ]


2. failing function
-------------------
[jvm.dll+0xe2896] translates back into jvm!PhaseCFG::set_pinned+0x76.


3. stacksize was only 256kB
---------------------------
 Hs_err_pid_log files show, that stack size was only 256kB.

Stack: [0x0000000006600000,0x0000000006640000),  sp=0x0000000006601000,  free space=4k

Comments
EVALUATION CompilerThreadStackSize is ignored on Windows in 1.4.2 and 5.0. 6.0 onwards respect this setting.
31-07-2007

WORK AROUND Increase stack size of ALL threads using e.g. -Xss4M *** (#1 of 1): [ UNSAVED ] ###@###.###
17-07-2007