-
Enhancement
-
Resolution: Fixed
-
P4
-
17
-
b03
With -XX:VerifyGCType it is currently possible to select particular kinds of GC pauses to verify (young, concurrent start, mixed, ...).
One useful additional verification type could be verification after an evacuation failure happened: evacuation failure is not very common, but executes significantly difference code - many failures in the past only occurred after evacuation failures.
Since evacuation failure is rather uncommon, using a particular existing type of GC pause (young, ...) wastes lots of time verifying pauses that are known to not be affected (and often causes the issue not appear because of overall less testing within the (typically) set runtime).
So the suggestion is to add a special verification type that selects (young) collections with an evacuation failure (applicable to VerifyAfterGC only of course) to speed up issue reproduction.
One useful additional verification type could be verification after an evacuation failure happened: evacuation failure is not very common, but executes significantly difference code - many failures in the past only occurred after evacuation failures.
Since evacuation failure is rather uncommon, using a particular existing type of GC pause (young, ...) wastes lots of time verifying pauses that are known to not be affected (and often causes the issue not appear because of overall less testing within the (typically) set runtime).
So the suggestion is to add a special verification type that selects (young) collections with an evacuation failure (applicable to VerifyAfterGC only of course) to speed up issue reproduction.
- relates to
-
JDK-8269078 Improve G1VerifyType naming
-
- Open
-