RFR: 8308507: G1: GClocker induced GCs can starve threads requiring memory leading to OOME [v6]

[Ivan Walulya]

On Fri, 2 Jun 2023 23:45:48 GMT, Albert Mingkun Yang <ayang at openjdk.org> wrote:

>> Ivan Walulya has updated the pull request incrementally with one additional commit since the last revision:
>> 
>>   remove newlines
>
> src/hotspot/share/gc/g1/g1VMOperations.cpp line 138:
> 
>> 136:   bool has_allocation_requests = !g1h->_stalled_allocations.is_empty();
>> 137:   if (has_allocation_requests) {
>> 138:     bool alloc_succeeded = g1h->handle_allocation_requests(false /* expect_null_mutator_alloc_region*/);
> 
> This eventually calls `expand`. On master, I believe `expand` is called always after a gc-cycle, based on the implicit assumption that running a gc-cycle is more desirable than expanding the heap.

Reset to preferring the gc pause over heap expansion.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/14077#discussion_r1218276770