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

[Ivan Walulya]

On Tue, 6 Jun 2023 13:39:21 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:
>> 
>>   prefer gc pause over heap expansion
>
> src/hotspot/share/gc/g1/g1CollectedHeap.cpp line 434:
> 
>> 432:   if (request.pending()) {
>> 433:     // GC Safepoint did not handle our allocation request. We should retry.
>> 434:     return false;
> 
> Is it possible for a thread to hit this point indefinitely, i.e. some form of starvation?

Only if you have indefinite triggering of non-allocating GCs. I wouldn't consider that starvation, as starvation here should imply some threads being able to allocate, and some other threads being unable to allocate even with allocation GCs triggered.

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

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