From owner-freebsd-java Wed Feb 19 7:42:25 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 567C137B401 for ; Wed, 19 Feb 2003 07:42:24 -0800 (PST) Received: from b.smtp-out.sonic.net (b.smtp-out.sonic.net [208.201.224.39]) by mx1.FreeBSD.org (Postfix) with SMTP id EF1A843FA3 for ; Wed, 19 Feb 2003 07:42:22 -0800 (PST) (envelope-from milo@cyberlifelabs.com) Received: (qmail 28445 invoked from network); 19 Feb 2003 15:42:22 -0000 Received: from turbo.sonic.net (208.201.224.26) by b.smtp-out.sonic.net with SMTP; 19 Feb 2003 15:42:22 -0000 Received: from cyberlifelabs.com (adsl-64-142-14-252.sonic.net [64.142.14.252]) by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id h1JFgMo17555 for ; Wed, 19 Feb 2003 07:42:22 -0800 X-envelope-info: Message-ID: <3E53A5DE.9080506@cyberlifelabs.com> Date: Wed, 19 Feb 2003 07:42:22 -0800 From: Milo Hyson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20030120 X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD Java Mailing List Subject: JVM choking Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 Has anyone run into any problems with their JVM choking on too many objects? I'm currently working on an application in which 1,000,000+ objects are in existence at any given time. When the program first starts up and begins creating the objects, things run very fast but soon begin to slow down. Available memory also drops rapidly. Eventually, everything grinds to a halt and it just sits there -- no disk activity, no network traffic, no output, but 100% CPU load. Several tens of megabytes of memory are still available so it's not out of RAM. After a minute or so of no activity, an exception begins to be displayed but never completes printing. There isn't enough of it shown to see what kind of exception it is. At that point, all I can do is hit Ctrl-C (which does kill it BTW). Anyone ever seen anything like this? I'm using the Native JDK 1.3.1 w/patchset 8. The problem occurs both with and without a JIT, but seems to get further without it. -- Milo Hyson CyberLife Labs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message