4239458 Details

****************************************************
Seems that we get an overflow in some integer arithmetic if the user
specifies a max heap size of 2048mb or beyond. This results in a sanity
check failing somewhere (negative heap size not allowed!).

It would be a shame to let a simple bug like an overflow stand in the way
of our users exploiting their 2+ gb systems. Or is this an attempt to
increase demands for 64 bit JVMs?

galileo 1003> java -mx2047m Hello
Hello - it works?!
8636168
galileo 1004> java -mx2048m Hello
Bad max heap size: -Xmx2048m
Could not create the Java virtual machine.


*****************************

Testing the same thing on kestrel gives same probles.

Anything above 2012 doesn't work. I have been getting 3 different error messages.

$ java -mx2012m Hello
Hello - it works?!

$ java -mx2013m Hello
Error occurred during initialization of VM
Could not reserve enough space for object heap

$ java -mx2046m Hello
Error occurred during initialization of VM
Size of maximum heap (-2147483648 bytes) must be aligned to 4194304 bytes

$ java -mx2048m Hello
Invalid maximum heap size: -Xmx2048m
Could not create the Java virtual machine.