jdk-1.4.2p7 crashes with no indication of why
Chuck Robey
chuckr at chuckr.org
Mon Mar 21 10:08:44 PST 2005
Nicolas Gieczewski wrote:
>>>-Xmx256m: Fine on Linux, random silent crashes on FreeBSD.
>>>-Xmx128m: java.lang.OutOfMemoryError exceptions on both OSs.
>>>
>>>Does this help at all? By now I'm pretty much sure that the crashes I'm
>>>experiencing are memory-management-related; otherwise they shouldn't
>>>go away when changing the value of -Xmx.
>>
>>Can you check what the 'top' and similar utilities report on the memory
>>usage of JVM close to the time of crashes, with 256M memory? Also, are
>>there more then one JVM running?
>>
>>(I'm asking this because there could be a resource limit you're hitting,
>>e.g. for maximum memory allowed to a process, or something like it.)
>
>
> The highest I've seen with top is SIZE/RES = 563M/234M, but that's not necessarily when it crashes. I've seen it crash at 559M/176M, for example, so it doesn't look like I'm hitting any specific limits.
>
Two items I am currently investigating:
First, the port complains that it couldn't find /bin/zip. No wonder, as
it's /usr/local/bin/zip. The quickest fix I wanted to try was a
softlink, so I did that, if it needs it, the *right* fix could come later.
Second, I cd'ed into work/control/make (might be there was an extra
component in there, I forget) and found out about WITH_LINUX_BOOTSTRAP,
which I had not seen before. I am using the Sun Linux jdk14 as a
bootstrap, so this seems like a likely thing, I set it, and then
restarted my build. I don't figure to get any good info from this for
some hours,
More information about the freebsd-java
mailing list