RFR: JDK-8324930: java/lang/StringBuilder problem with concurrent jtreg runs

[Matthias Baesken]

On Tue, 30 Jan 2024 09:08:28 GMT, Matthias Baesken <mbaesken at openjdk.org> wrote:

> On some Windows machines we see sometimes OOM errors because of high resource (memory/swap) consumption. This is especially seen when the jtreg runs have higher concurrency. A solution is to put the java/lang/StringBuilder tests in the exclusiveAccess.dirs group so that they are not executed concurrently, which helps to mitigate the resource shortages.
> Of course this has the downside that on very large machines the concurrent execution is not done any more.

It happens on various machines, two for example

 Windows Server 2022 Standard     16 cores  32G  RAM
 Windows Server 2019 Standard     16 cores  32G  RAM

On both machines we run :tier1  -avm  with  -conc:15   (concurrency jtreg flag) .

> The other unanswered question is - why is this happening now?

I filed the issue this year but there are a couple of occurrences also from last year.  
I find also similar older failures  from 2022 of  java/lang/StringBuilder/HugeCapacity.java because of resource shortages (but those did not generate a hserr file for some reasons just some text output).
So the issue is there for months already (maybe years?) .

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

PR Comment: https://git.openjdk.org/jdk/pull/17625#issuecomment-1952490909