committed > max in MemoryMXBean#getHeapMemoryUsage()

[Thomas Schatzl]

On Fri, 2018-07-13 at 10:30 +0200, Daniel Mitterdorfer wrote:
> Hi Erik,
> > 
> > Do you any kind of GC logging from the test run where you
> > encountered the bug?
> 
> Unfortunately, we don't have GC logging enabled by default in our
> test suite so the exception trace is all I got. I am now repeatedly
> running the test suite with the original flags (-Xms512M -Xmx512M)
> and also added the following logging configuration:
> 
> -Xlog:gc*=trace,heap*=trace,tlab*=off:stdout:time,pid,tid,level,tags
> 
> As soon as I get another failure, I'll provide the full log file.
> Please let me know if you need any other logs (i.e. whether I should
> adjust my log configuration).

  I think these flags are fine.

Since Erik and me strongly believe the issue is with the relevant G1
code Erik mentioned we will reassign the bug to us (he said there is
already a bug reported on it).

Thanks a lot,
  Thomas