RFR: 8289764: gc/lock tests failed with "OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects" [v2]

[Leonid Mesnik]

On Mon, 8 Aug 2022 16:04:19 GMT, Ramkumar Sunderbabu <rsunderbabu at openjdk.org> wrote:

>> exactly, however, the whole 'engageGC' method will be executed only once and always work in this loop.
>> So the combination of lock/engageGC()/unlock is executed only once and the test spends all it's time in 'engageGC' which is not the stress for lock/unlock and moreover could cause OOME if lock/unlock really locks GC.
>
> so this is the algorithm you are getting at?
> while( test.duration ) {
>   lock
>   engageGC (100 youngGC and 1 fullGC)
>   unlock
> }

Yes. It is what test should do.

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

PR: https://git.openjdk.org/jdk/pull/9658