Date: Tue, 22 Mar 2005 13:17:07 -0700 From: Greg Lewis <glewis@eyesbeyond.com> To: Nicolas Gieczewski <trash@nixsoftware.com> Cc: Ivan Voras <ivoras@fer.hr> Subject: Re: jdk-1.4.2p7 crashes with no indication of why Message-ID: <20050322201707.GB91212@misty.eyesbeyond.com> In-Reply-To: <013e01c52e40$29ecb310$0200a8c0@ash> References: <00e201c52907$41af13f0$0200a8c0@ash> <20050316163228.GA58595@misty.eyesbeyond.com> <04bb01c52b0d$0ab3ec60$0200a8c0@ash> <423EBD98.2010907@fer.hr> <013e01c52e40$29ecb310$0200a8c0@ash>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 21, 2005 at 03:02:24PM -0300, Nicolas Gieczewski wrote: > 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. I don't suppose you have a small test app or some other way of reproducing the problem? That would be helpful. Saving that, running things with java_g and gdb would be helpful. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050322201707.GB91212>