From owner-freebsd-java Tue Dec 8 14:04:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17880 for freebsd-java-outgoing; Tue, 8 Dec 1998 14:04:31 -0800 (PST) (envelope-from owner-freebsd-java@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17869; Tue, 8 Dec 1998 14:04:27 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id PAA22269; Tue, 8 Dec 1998 15:04:22 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id PAA14247; Tue, 8 Dec 1998 15:04:21 -0700 Date: Tue, 8 Dec 1998 15:04:21 -0700 Message-Id: <199812082204.PAA14247@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mahadevan Iyer Cc: Nate Williams , java-port@FreeBSD.ORG, freebsd-java@FreeBSD.ORG, saurabh@internetdevices.com, namit@internetdevices.com Subject: Re: Possible Bug in JVM Garbage Collection of Threads In-Reply-To: <366D9F1D.29759389@internetdevices.com> References: <36381ADB.DCCDAB3D@internetdevices.com> <199811091741.KAA04801@mt.sri.com> <36472A9A.A1661625@internetdevices.com> <199811091759.KAA04986@mt.sri.com> <366D9F1D.29759389@internetdevices.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > here is another one. This one is pretty critical and any help will be > deeply appreciated > > FreeBSD JVM version : 1.1.7 > This code causes the Resident memory size of the java process to continously > grow > You can see this if you run "top" on freeBSD > It will eventually given an OutOfMemoryError I see this on Solaris as well. > If you throw in the socket code, it will give a "recursive malloc()" error > To trigger this error there has to be a client that continuously tries to > connect to the server > This problem seems to be an result of the previous problem, however this > causes our server to die. > > I ran this using a SUN JVM on Solaris without any problems I just ran it and I *do* see this problem, which implies a generic JVM problem with the SUN implementation. Which version of the JVM are you using on Solaris? % java -fullversion java full version "JDK1.1.7M" % Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message