While investigating 6899058 and 6902155 I turned on the G1PolicyVerbose flag by setting it to '2' in order to get verbose information about the various HeapRegions and their particular roles (young, survivor, non-young, gc-alloc etc) while running the test case. Setting G1PolicyVerbose=2 causes a SIGSEGV in CollectionSetChooser::printSortedHeapRegions. The code in that routine does not take into account that there are null entries in the _markedRegions growable array. If we look at the verify routine, only the entires between _curMarkedIndex and _numMarkedRegions are non-null.
|