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

[Ivan Walulya]

On Tue, 23 May 2023 09:21:04 GMT, Ivan Walulya <iwalulya at openjdk.org> wrote:

>> Just an idea: I think it would be nicer and more understandable if the code explicitly checked if the object is part of the stalled allocation requests instead of relying on it being a filler object.
>> It is a bit ugly that we use filler objects to identify objects in construction here, given that "nobody should have a reference to it" (I see the need). It is somewhat okay since it's GC.
>> Another option would be having dedicated "object-in-construction" objects, which is more work.
>
> In the worst case, searching the satisfied allocation requests list might have performance implications. However, that is speculation for now, I haven't tried it.

Added the explicit check for unclaimed allocations

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

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