From owner-freebsd-java@FreeBSD.ORG Mon Mar 21 18:01:58 2005 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DF2A16A4CE for ; Mon, 21 Mar 2005 18:01:58 +0000 (GMT) Received: from srv04.bkmedia-hosting.com (srv04.bkmedia-hosting.com [69.57.140.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0A1643D67 for ; Mon, 21 Mar 2005 18:01:57 +0000 (GMT) (envelope-from trash@nixsoftware.com) Received: from ash (host82.201-252-74.telecom.net.ar [201.252.74.82]) (authenticated (0 bits))j2LI1dq13907; Mon, 21 Mar 2005 19:01:40 +0100 Message-ID: <013e01c52e40$29ecb310$0200a8c0@ash> From: "Nicolas Gieczewski" To: References: <00e201c52907$41af13f0$0200a8c0@ash> <20050316163228.GA58595@misty.eyesbeyond.com> <04bb01c52b0d$0ab3ec60$0200a8c0@ash> <423EBD98.2010907@fer.hr> Date: Mon, 21 Mar 2005 15:02:24 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4946.1400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4946.1400 cc: Ivan Voras Subject: Re: jdk-1.4.2p7 crashes with no indication of why X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 18:01:58 -0000 > > -Xmx256m: Fine on Linux, random silent crashes on FreeBSD. > > -Xmx128m: java.lang.OutOfMemoryError exceptions on both OSs. > >=20 > > 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. >=20 > Can you check what the 'top' and similar utilities report on the = memory=20 > usage of JVM close to the time of crashes, with 256M memory? Also, are = > there more then one JVM running? >=20 > (I'm asking this because there could be a resource limit you're = hitting,=20 > e.g. for maximum memory allowed to a process, or something like it.) The highest I've seen with top is SIZE/RES =3D 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. Nick