RFR (M): 8207200: Committed > max memory usage when getting MemoryUsage
Thomas Schatzl
thomas.schatzl at oracle.com
Fri Aug 24 10:17:15 UTC 2018
Hi,
ping! :)
On Wed, 2018-08-08 at 17:15 +0200, Thomas Schatzl wrote:
> Hi all,
>
> can I have reviews for this change that fixes some races when
> reading from G1MonitoringSupport members, causing some assertion
> failing after weeks of running some programs that poll the G1
> MemoryPools.
>
> It does so by adding a mutex that is held during reading and writing
> them.
>
> There is also a new explicit call in CollectedHeap to get a
> consistent overall MemoryUsage information instead of the existing
> code looping over the heap's memory pools. That one is problematic
> too otherwise.
>
> There is still no change in the calculation of the values of the
> MemoryUsage members.
>
> CR:
> https://bugs.openjdk.java.net/browse/JDK-8207200
> Webrev:
> http://cr.openjdk.java.net/~tschatzl/8207200/webrev
> Testing:
> hs-tier1-4,jdk-tier1-3
>
> This change is based on the changes for JDK-8209062.
these changes have been pushed by now.
Thanks,
Thomas
More information about the hotspot-gc-dev
mailing list