RFR (S): 7112912:Message "Error occurred during initialization of VM" on boxes with lots of RAM

Tao Mao tao.mao at oracle.com
Thu Mar 21 15:42:15 PDT 2013



On 3/18/13 12:59 AM, Thomas Schatzl wrote:
> Hi all,
>
>    here is a new webrev for this issue. Changes are:
>
> - merged code for os::has_allocatable_memory_limit of linux/bsd/solaris
> into a single method.
So, where is the merged routine now?
> - on 32 bit targets that method now tries to find the maximum
> allocatable virtual memory limit by performing a binary search. In this
> search, the method tries to find the largest allocatable block of
> memory, and returns this size as limit.
> It uses a binary search to do this. The old mechanism relied on some
> manually determined number (2*G - 2*LargePageSize)
> - fixed the description of MaxVirtMemFraction
> - rename Arguments::allocatable_physical_memory() to
> limit_by_allocatable_memory().
> - the argument of os::has_allocatable_memory_limit() is now passed as
> address.
> - removed some obsolete comment
>
> Tests: JPRT, manual testing on linux 32/64 bit, BSD 64 bit, Windows
> 32/64 bit. Additional manual testing targeted at the maximum memory
> limit search on linux 32 bit.
>
> Webrev:
> http://cr.openjdk.java.net/~tschatzl/7112912/webrev.1/
>
> CR:
> http://bugs.sun.com/view_bug.do?bug_id=7112912
>
> JIRA:
> https://jbs.oracle.com/bugs/browse/JDK-7112912
>
> Thanks,
>    Thomas
>
>
>


More information about the hotspot-gc-dev mailing list