During PIT testing for jdk7 b79, the test case mentioned in 6899058 failed. As a result the fixes for 6899058 and 6908215 (which used the same test case) were recorded as PIT failures with G1.
An email from Leonid Mesnik indicated that the test case mentioned in 6899058 (gcl001) had failed with the same assertion as that reported in 6899058. More frequently, however, the test case would hang.
Here is Leonid's email:
I am trying to verify the 6899058 G1: Internal error in ptrQueue.cpp:201 in nightly tests
for hsx 17 PIT b06 jdk7b79 with runnig test gcl001 on the vm-x2270-01 (I tried other machines and solaris but situation is the same) with command:
/net/sqenfs-1.sfbay/export1/comp/vm/jdk/hsx/17/pit/b06/jdk7b79/fastdebug/linux-amd64/bin/java -d64 -server -Xmixed -XX:+PrintGCDetails -XX:-UseCompressedOops -XX:-PrintVMOptions -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -Djava.library.path=/net/sqenfs-1.sfbay/export1/comp/vm/testbase/sqe/vm/6/build/execution/vm//bin/lib/linux-amd64/nsk/stress/jni/gclocker -cp /net/sqenfs-1.sfbay/export1/comp/vm/testbase/sqe/vm/6/build/execution/vm//bin/classes nsk.stress.jni.gclocker.gcl001
Unfortunately sometimes I get the same crash:
[GC pause (young)# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc: SuppressErrorAt=/ptrQueue.cpp:217
# A fatal error has been detected by the Java Runtime Environment:
# Internal Error (/tmp/jprt/P1/B/141120.et151817/source/src/share/vm/gc_implementation/g1/ptrQueue.cpp:217), pid=7322, tid=139670985931088
# Error: guarantee(completed_buffers_list_length() == _n_completed_buffers,"Completed buffer length is wrong.")
# JRE version: 7.0-b78
# Java VM: Java HotSpot(TM) 64-Bit Server VM (17.0-b06-2009-12-23-141120.et151817.hs17b06-fastdebug mixed mode linux-amd64 )
# An error report file with more information is saved as:
# If you would like to submit a bug report, please visit:
Current thread is 139670985931088
or more often VM just "hangs" during and I am not able to get any stack info. When I use -XX:G1PolicyVerbose=2 the last messages which it prints are:
(3955928 KB left in heap.)
Added [0x00007f763c800000, 0x00007f763c900000) to CS.
(3955752 KB left in heap.)
New alloc region [0x00007f763a600000, 0x00007f763a600000, 0x00007f763a700000) for survivors: A F 13 space 1024K, 0% used [0x00007f763a600000, 0x00007f763a600000, 0x00007f763a700000)
New alloc region [0x00007f763a500000, 0x00007f763a500000, 0x00007f763a600000) for survivors: A SU F 13 space 1024K, 0% used [0x00007f763a500000, 0x00007f763a500000, 0x00007f763a600000)
after it VM just hangs.
Could you please check if I does not run it correctly or something like this? or should I file new CR for this issue?