Alan Bateman said the following on 02/02/11 20:05:
David Holmes wrote:
It looks like this was actually fixed under 6840305 back in July 2009:
http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/8c79517a9300
This CR was not updated however.
Does the problem still exist?
David Holmes
I think this is separate and 6853676 is about
com.sun.management.OperatingSystemMXBean. The code for that is in jdk
repo in src/windows/native/com/sun/management. It should be using
GlobalMemoryStatusEx rather than GlobalMemoryStatus.
Thanks Alan, the comments in 6853676 led me astray.
As a P4 it looks like this has just slipped through the cracks.
David
Dmytro - to your question, serviceability-dev is the right place to
bring it.
-Alan
