OOM Errors in 8GB JVM builds, -XX:SoftMaxHeapSize

[Fabian Huch]

>>
>> Since we are using the Z garbage collector, I've now changed the 
>> build manager to use its soft heap max size (8g) with a hard limit of 
>> 32g.
>
> I was not aware of that fine point. Would you say that the Z garbage 
> collector is where high-end Java applications are going,
I would expect most desktop applications to migrate to generational ZGC. 
Latency is better than G1GC, it's more efficient, and allows for desktop 
applications with a low memory footprint. That solves all the main 
problems with JVM garbage collection.
> and that its extra options work properly?

I have never seen JVM options misbehave. The only caveat is that this is 
an XX option, i.e. subject to change without notice (but typically even 
those remain stable).


Fabian