diablo 1.5 died after 5 day uptime

[Vadim Goncharov]

26.05.06 @ 01:09 Kurt Miller wrote:

>> I have an SMP (HTT) machine with 5.5-PRERELEASE, using official diablo  
>> 1.5 jdk
>> binaries from beginning of April. As suggested, I now run java with
>> -XX:+UseMembar cmdline switch, that resolved problem with crashing
>> application after startup.
>> But today after 5 days uptime now-debugged-and-set-to-long-run server
>> process
>> have crashed, with 100M coredump file. What happened? Below are log and
>> gdb backtrace.
>> As some additional info: I have limits in login.conf, 32M for resident  
>> size
>> and 256M for virtual mem size; yesterday when I looked at process stats
>> it was about 10M resident and 250M virtual - could be a reason?..
>
> Hi,
>
> It does appear that you've run out of vm.
>
> <snip>
>> #21 0x0a3fceda in vm_exit_out_of_memory ()
>>     from /usr/local/diablo-jdk1.5.0/jre/lib/i386/client/libjvm.so

But so why it dies on signal 11 with scary logs and coredump, instead of
descriptive out-of-memory diagnostics and graceful shutdown? Isn't that
a bug ?

-- 
WBR, Vadim Goncharov