Hotspot crash

[Steve Poole]

hi Volker  -  the machine in question is completely dedicated to building OpenJDK and doesn't do anything else.   
Since it a single threaded machine any memory usage is coming from (in theory) the build process.

May be we really are pushing it too hard :-)    The same machine can build the classes using J9 though so its a little strange...

If you're comfortable that it not a hotspot  problem I'll do the diagnostics.

let you know what I find out.



On 11 Feb 2013, at 18:41, Volker Simonis <volker.simonis at gmail.com> wrote:

> Hi Steve,
> 
> unfortunately I was quite busy today so I just looked at the crash.
> 
> I agree that the warning are annoying and we will switch them off if
> we will be not running with -XX:+Verbose.
> But as far as I can see, they are basically harmless. The appear
> because we've switched on compressed pointers by default on AIX and
> whtat happens is that at startup the VM tries to find some "good"
> addresses for the allocation of the heap. If this doesn't succeed (and
> that's what the warnings basically say) that's no real problem. As I
> said, it's annoying and we will switch them off. Until then you can
> use the switch "-XX:-UseCompressedOops" to switch compressed pointers
> off manually.
> 
> Regarding the actual error I'm a little bit confused. In that special
> code the VM is actually only calling the bare os "malloc" functions
> which seems to be unable to allocoate native memory. Does the VM fail
> reproducible with this error? I saw in the hs_err.log file that the
> machine is under high load:
> 
> load average:20.07 17.96 17.18
> 
> and the swap memory is nearly exhausted:
> 
> 
>  physical total : 32212254720
>  physical free  : 5296439296
>  swap total     : 536870912
>  swap free      : 483180544
> 
> while the machine still has 5 GB of free ram. Maybe, at the point
> where malloc was called there where other processes running which used
> additional memory?
> 
> Would it be possible to carve out the javac command which leads to the
> error (i.e."Compiling 733 files for BUILD_FULL_JAVAC")
> 
> Otherwise I'll try to reproduce it myself.
> 
> Regards,
> Volker
> 
> 
> On Sun, Feb 10, 2013 at 9:04 PM, Steve Poole <spoole at linux.vnet.ibm.com> wrote:
>> hi guys - I'm getting a crash (basically native out of memory) when trying to build JDK8 on AIX with latest and greatest JDK7u build.
>> 
>> I built the jdk7u one myself according to the published instructions on Volkers cr page.
>> 
>> The crash and log are available here    (build log at http://cr.openjdk.java.net/~spoole/log.txt    crash at http://cr.openjdk.java.net/~spoole/hs_err_pid13369358.log )
>> 
>> The machine has 30GB of memory and what with the amount of warnings showing up I'm assuming its a bug :-)
>> 
>> Let me know if there is anything I can do to work around this (or if you need more info)   I'm trying to use the autoconf process for JDK8 and this my first major hurdle.   Any help would be appreciated!
>> 
>> Thanks
>> 
>> Steve
>