From owner-freebsd-java Thu Feb 20 0:41:35 2003 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 8650437B401 for ; Thu, 20 Feb 2003 00:41:34 -0800 (PST) Received: from seed.net.tw (sn14.seed.net.tw [139.175.54.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id B51C243FA3 for ; Thu, 20 Feb 2003 00:41:32 -0800 (PST) (envelope-from leafy@leafy.idv.tw) Received: from [211.74.135.107] (port=49196 helo=leafy.idv.tw) by seed.net.tw with esmtp (Seednet 4.10:3) id 18lmGp-000JZ7-00 for freebsd-java@FreeBSD.ORG; Thu, 20 Feb 2003 16:41:31 +0800 Received: from leafy.idv.tw (nobody@localhost [127.0.0.1]) by leafy.idv.tw (8.12.7/8.12.7) with ESMTP id h1K8fU72001750 for ; Thu, 20 Feb 2003 16:41:30 +0800 (CST) (envelope-from leafy@leafy.idv.tw) Received: (from leafy@localhost) by leafy.idv.tw (8.12.7/8.12.7/Submit) id h1K8fU4e001749 for freebsd-java@FreeBSD.ORG; Thu, 20 Feb 2003 16:41:30 +0800 (CST) Date: Thu, 20 Feb 2003 16:41:30 +0800 From: leafy To: FreeBSD Java Mailing List Subject: Re: JVM choking Message-ID: <20030220084130.GA1733@leafy.idv.tw> Mail-Followup-To: FreeBSD Java Mailing List References: <3E53A5DE.9080506@cyberlifelabs.com> <20030220001813.A51537@phantom.cris.net> <3E54939B.5080104@cyberlifelabs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Disposition: inline In-Reply-To: <3E54939B.5080104@cyberlifelabs.com> User-Agent: Mutt/1.5.3i Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Feb 20, 2003 at 12:36:43AM -0800, Milo Hyson wrote: > I've determined the problem to be an out-of-memory condition in the JVM > (if I wait long enough it spits out an exception). It's curious however > that the OS still reports having quite a lot of RAM free. I ran the > attached test code without any command-line arguments and had the > following results: > > > It would appear that the memory manager in both JVMs is hitting some > sort of self-imposed limitation, as neither OS was anywhere near running > out of memory. Where exactly that limit is set seems to depend on which > JVM is used. > > -- > Milo Hyson > CyberLife Labs It might be running out of heap space. Have you tried to increase the heap size for the VM? Jiawei Ye -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message