JDK-6867250 : G1: java.lang.ArrayIndexOutOfBoundsException in Win64
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: hs16
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_2003
  • CPU: x86
  • Submitted: 2009-07-31
  • Updated: 2013-09-18
  • Resolved: 2010-05-05
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 :  
Relates :  
Relates :  
Description
Regression after 6700789 changes.

C:\cfang>VM_kvn\bin\java -server -Xmx128M -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:AbortVMOnException=java.lang.ArrayIndexOutOfBoundsException -XX:+PrintCompilation -XX:CICompilerCount=1 -Xbatch -XX:+TraceDeoptimization -XX:CompileCommand=print,java.util.ArrayList::add -XX:-Verbose -XX:+PrintGCDetails -jar GCBasher.jar -time:60000

# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc:  SuppressErrorAt=\exceptions.cpp:378
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (C:\temp\jprt\P1\B\224354.ysr\source\src\share\vm\utilities\exceptions.cpp:378), pid=3532, tid=664
#  Error: Saw java.lang.ArrayIndexOutOfBoundsException, aborting
#
# JRE version: 7.0-b66
# Java VM: Java HotSpot(TM) 64-Bit Server VM (16.0-b05-2009-07-14-224354.ysr.coops-fastdebug mixed mode windows-amd64 )
# An error report file with more information is saved as:
# C:\cfang\hs_err_pid3532.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#

Comments
EVALUATION As this failure seems to be caused by a marking failure, it's very likely it's been fixed by one of three marking bugs we recently identified and fixed: 6940310: G1: MT-unsafe calls to CM::region_stack_push() / CM::region_stack_pop() 6935821: G1: threads created during marking do not activate their SATB queues 6909756: G1: guarantee(G1CollectedHeap::heap()->mark_in_progress(),"Precondition.") I'm closing this as a dup.
05-05-2010