6853676: OperatingSystemMXBean.TotalPhysicalMemorySize has incorrect value

David Holmes David.Holmes at oracle.com
Wed Feb 2 01:47:07 PST 2011


Dmytro,

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

Dmytro Sheyko said the following on 02/02/11 19:34:
> Hi,
> 
> Any updates on it?
> 
> I don't want to be overly importunate, but the quite trivial fix was 
> available year ago.
> Maybe I do something wrong, so please suggest what I should do to have 
> this bug fixed.
> 
> Thanks,
> Dmytro
> 
> ------------------------------------------------------------------------
> From: dmytro_sheyko at hotmail.com
> To: serviceability-dev at openjdk.java.net
> Subject: 6853676: OperatingSystemMXBean.TotalPhysicalMemorySize has 
> incorrect value
> Date: Fri, 28 Jan 2011 15:05:45 +0700
> 
> Hi,
> 
> I would like to find sponsor and discuss fix for bug#6853676
> OperatingSystemMXBean.TotalPhysicalMemorySize has incorrect value
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6853676
> 
> The idea is to use GlobalMemoryStatusEx instead of GlobalMemoryStatus.
> 
> patch is available here:
> https://bugs.openjdk.java.net/show_bug.cgi?id=100077
> 
> Thanks,
> Dmytro
> 


More information about the serviceability-dev mailing list