JDK-6983892 : nsk.stress.stack.stack008.stack008 crashes starting JDK7 b108
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: hs19
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris
  • CPU: x86
  • Submitted: 2010-09-10
  • Updated: 2012-02-01
  • Resolved: 2011-01-04
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.
JDK 7
7Resolved
Related Reports
Duplicate :  
Relates :  
Relates :  
Description
nsk.stress.stack.stack008.stack008 crashes with JDK7b108.

Test output is: 
Max. depth: 1200
# Test level exit status: 11

The crash is observed on solaris-x86. 
The test crashes with 7b109 also.
Seems like the problem relates to compiler changes.

The core file and shallow automatic analysis results are here:
http://vmsqe.russia.sun.com/execution/results/JDK7/PROMOTION/VM/7/b108/G1/vm/solaris-i586/server/mixed/solaris-i586_vm_server_mixed_nsk.stack.testlist/ResultDir/stack008/

Comments
EVALUATION I went to this directory and the information from the crash claim that it's still hs19-b05. The fix for 6975049 was in b06. % cd /net/vmsqe.russia/export/execution/results/JDK7/PROMOTION/VM/7/b108/G1/vm/solaris-i586/server/mixed/solaris-i586_vm_server_mixed_nsk.stack.testlist/ResultDir/stack008 % more jinfo.core Attaching to core ./ResultDir/stack008/core from executable /export/local/common/jd k/baseline/solaris-i586/bin/java, please wait... Debugger attached successfully. Server compiler detected. JVM version is 19.0-b05 Java System Properties: ... And from the pstack.core in that directory, the symptoms match the other bug as well with a stack overflow coming from the thread with: __1cNSharedRuntimeXgenerate_native_wrapper6FpnOMacroAssembler_nMmethodHandle_iipnJBasicType_pnJVMRegPair_4_pnHnmethod__ So this is definitetly fixed and it's a duplicate.
04-01-2011