hg: jdk7/hotspot-rt/hotspot: 6840305: Discrepancy in system memory details (when 4G or greater) reported by JVM and Windows OS

[Dmytro Sheyko]

Hi,

I would note that this is not the only place where GlobalMemoryStatus() is used instead of GlobalMemoryStatusEx().
Please have a look at
OperatingSystemMXBean.TotalPhysicalMemorySize has incorrect value
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6853676
https://bugs.openjdk.java.net/show_bug.cgi?id=100077

Hope that due to similarity with the former one, this bug has a chance to be fixed soon as well.

--
Dmytro Sheyko

> From: poonam.bajaj at sun.com
> To: jdk7-changes at openjdk.java.net; hotspot-runtime-dev at openjdk.java.net; serviceability-dev at openjdk.java.net
> Subject: hg: jdk7/hotspot-rt/hotspot: 6840305: Discrepancy in system memory	details (when 4G or greater) reported by JVM and Windows OS
> Date: Fri, 17 Jul 2009 14:39:46 +0000
> 
> Changeset: 8c79517a9300
> Author:    poonam
> Date:      2009-07-16 18:21 -0700
> URL:       http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/8c79517a9300
> 
> 6840305: Discrepancy in system memory details (when 4G or greater) reported by JVM and Windows OS
> Summary: GlobalMemoryStatus() does not report correct memory usage when the system has more than 4gb of RAM. GlobalMemoryStatusEx() should be used in place of GlobalMemoryStatus().
> Reviewed-by: kamg, coleenp
> 
> ! src/os/windows/vm/os_windows.cpp
> 

_________________________________________________________________
Show them the way! Add maps and directions to your party invites. 
http://www.microsoft.com/windows/windowslive/products/events.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/serviceability-dev/attachments/20090720/df95cac4/attachment.html