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

Ramkumar Sunderbabu rsunderbabu at openjdk.org
Mon Aug 8 16:08:02 UTC 2022


On Mon, 8 Aug 2022 15:58:06 GMT, Leonid Mesnik <lmesnik at openjdk.org> wrote:

>> Loop won't run for just once. It will run for the duration of the test. If the test is configured to run, say, 2 mins, stresser.continueExecution() will be false after 2 mins.
>
> 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
}

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

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


More information about the hotspot-dev mailing list