Unexpected system GCs with Semeru 17.0.10

[gjdeval]

Issue 19152 reported Liberty slow start with Semeru 17.0.9.
Starting the same configuration with Semeru 17.0.10 results in many unexpected system GCs during startup - by contrast, starting with Semeru 17.0.9 caused no system GCs, and no global GCs. The "extra" system GCs with Semeru 17.0.10 all have reason "rasdump" which is confusing since no dumps were generated.

Verbose GC logs for startup of a Liberty configuration with Semeru 17.0.9 and Semeru 17.0.10 are attached.

verbosegc.137819.001.JDK17.0.9.log
verbosegc.137595.001.JDK17.0.10.log

[dmitripivkine]

In the process of doing classes retransformation VM calls SystemGC to eliminate dark matter and walks objects in the heap. This is intentional but not effective enough unfortunately.
@jdmpapin and @TobiAjila currently working for better approach for 0.44. We hope this fix should not touch GC code.

[pshipton]

For tracking, the gc was introduced/modified by the following added in 17.0.10
#18236
#18762
which fixed issues with the following added in 17.0.9
#17850

[jdmpapin]

Fixed in #19187
0.44: #19213
JDK next: ibmruntimes/openj9-openjdk-jdk#759
JDK22: ibmruntimes/openj9-openjdk-jdk22#35
JDK21: ibmruntimes/openj9-openjdk-jdk21#136
JDK17: ibmruntimes/openj9-openjdk-jdk17#333